Unburdening Testing – Finding the Balance Point for Test Documentation
Fiona Charles
Quality Intelligence
Do you believe you have to produce too much documentation for your testing? Too little? Or just about the right amount? Do you find yourself mired in wasteful effort filling in boilerplate and copying text from one heavyweight document only to paste it into the next? Before they even get their hands on the software they’re going to test, many testers are expected to deliver some or all of the following: A test project schedule, a master test plan, test strategy, test cases, and a test execution plan
Yet other testers working on Agile teams may find themselves pressured to skip documentation they believe is essential to their testing. The tester’s product is information for stakeholders about the software under test. To make the most productive use of our time and serve our stakeholders effectively, we need to find a balance point for test documentation: just enough; not too little or too much. In this webinar, we will look at some ways to do that.
Key Takeaways:
- Learn how to find a balance point for test documentation
- Get the most productive use out of your time
About Me!
Fiona Charles teaches IT practitioners project skills “beyond process”-hands-on practical skills essential to thrive and excel on any kind of software project. An expert test consultant and manager, she has been in the thick of the action through 30+ years of challenging projects across the business spectrum on both sides of the Atlantic. Throughout her career, Fiona has advocated, designed, implemented and taught pragmatic and humane practices to deliver software worth having. Fiona’s articles and blog posts appear frequently, and she conducts experiential workshops at international conferences, and in-house for clients. In 2011, Fiona conducted an experiential tutorial on “Delivering Difficult Messages” at the EuroSTAR conference. Contact Fiona via her websitewww.quality-intelligence.com, and follow her on twitter @FionaCCharles.