Forum Discussion
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!
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
- 3 days agovladd1