For day 12 of 30 days of agile testing I’ve had quite a varied range of experiences across different companies related to documentation.
My previous company our test documentation was really detailed, too detailed in the beginning. Steps for a login screen test case, for example, would be:
- Navigate to page.com/login
- Enter username “User1”
- Enter password “Password1.”
- Click “Login” button
Then there would be a test case for a user not in the system, another for empty login credentials, one for special characters.
We moved away from that after a while to a move checklist style of guidance written as a comment on the user story. Going back to the login example,
- Check existing user
- Check non existing user
- Check empty fields
When I had checked these I would update the comment to add in what I had tried and that the expected results were achieved if that was the case. This method seemed to be easier for the whole team to follow and freed up more time to test than writing documentation.
In my current job, the only test documentation I have is my automation suite and my terribly written notes from exploratory testing. Our user stories have no acceptance criteria but occasionally I’ll have some attachments from our UX person of what the UI should look like. Back to the agile manifesto “Working software over comprehensive documentation” I think we’ve taken this to the extreme but I’m not sure how to best document in a continuous delivery environment. I don’t want to write documentation for the sake of it because I’ve learned already that it’s just a massive waste of time.
What test documentation do you have? Do you use tools like Zephyr or TestRail? Would improving it be easy or do you think you’d need more buy in?