Forum Discussion
We don't document our exploratory testing much. We have a high level test plan that's developed by the group and attached to the JIRA ticket that has the story/task. The tests in TestComplete have enough comments and log entries in them that a user familiar with the software would understand them. The ticket also contains links to a log of a successful test run and a link to the test in svn.
We don't expect that a brand new person would be able to pick up where an experienced person left off. I started here when everything was documented step by step in Excel sheets and it really wasn't that much help until I had actual user training on the software.
Agreed, Marsha_R... sometimes the amount of documentation we do as testers IS excessive. But it will vary from shop to shop and situation to situation. That's the thing about Agile is that it has a lot of adaptability. It's driven by the needs of the team doing the work... and each team make up is just a LITTLE bit different. :)
If I have enough documentation and artifacts created to get my friend from my house to my office with all the contingencies covered, then it's enough. Don't do more than what is needed... but certainly, I would not consider it a waste of time if it IS needed.
Cheers!
- Marsha_R8 years agoChampion Level 3
tristaanogre Yes, exactly!
I should also mention that we are audited by customers several times a year and we are also ISO certified and our documentation serves to get us through those audits with flying colors.
Do the documentation that you *need* but always figure out if it's actually needed. Make sure it will be useful before you spend a lot of time and energy on docs that no one will ever see. Maybe you can get some of that time back to do actual testing!
- tristaanogre8 years agoEsteemed Contributor
One more note on detailed documentation... especially if you need to convert a manual test case into automation. If the test case doesn't have enough information to pass off to the person doing the automation, it's not documented with enough detail. Again, that level of detail may vary from place to place, but that is also something that need to be taken into consideration, especially concerning the OP on how to incoporate TestComplete into an Agile environment.
- Marsha_R8 years agoChampion Level 3
tristaanogre We address that in our planning meetings. Our whole group goes through the tickets and everyone asks questions then so everyone hears the answers. We do our best to get the details in there at the start, but occasionally a programmer will pick up a ticket and none of us will remember the meaning of that cryptic comment that was so clear before. :smileylol:
Related Content
Recent Discussions
- 5 hours agoSvetaG