Recently, I want to learn more about how Testers are gathering their testing artifacts to help them make a decision on whether the code they are testing is ready to go to production. As Testers we know we will never be able to cover all of the potential tests. People outside of testing often have a hard time understanding why full testing coverage can be impossible especially for larger modules / functionality we are testing. This includes the sheer number of tests to perform, understanding the critical risks, what is important to the customer, among other considerations and then balancing all of that with time available for testing. Recording your testing may seem scary or intimidating at first, but it can have a lot of benefits. A recording can be used when working with a Developer on how to reproduce a problem; demonstrating to another Tester what you saw in testing to determine next steps; and providing physical evidence during an audit.
Recording your testing may or may not help defend your sampling strategy but if you add journal notes with your recordings you may be able to show the progression of your testing and why you made certain decisions. This can be important when you need to go back to review why you made certain decisions or review how you tested something. Most of us cannot rely on our memory to remember why we made certain decisions. Therefore, a certain level of documentation is important.
Understanding why and how we document information is important. A great starting point to understand more about how and why Testers collect journal notes is discussed in Michael Bolton’s article: An Exploratory Tester’s Notebook.
Another great article Have You Considered Evidence of Testing?
I have had a lot of informative conversations with Griffin Jones on the importance of gathering testing evidence. Please refer to his session talk at CAST 2013 What is good evidence? You can learn more about Griffin’s consulting business Congruent Compliance by clicking here.
You can find even more information from Software Testing Club where Testers shared their thoughts on recording tools by clicking here.
I gathered, through social medial, what video recording and documentation tools Testers are using to gather their testing artifacts. I would like to thank the following people for responding: Teri Charles, Raji, Gagan Talwar, Mohinder Khosla, Ajay Balamurugadas, Richard Bradshaw, Lisa Crispin, Srinivas Kadiyala, Adam Yuret, and Griffin Jones. As always, we have an awesome Testing Community that is always willing to share information.
Below is a summary of the findings. Some of these tools are open source and others you must purchase but they may have a short trial period. I would suggest identifying what is important to you in a recording tool before you start your evaluation to make a better decision.
- Debut video capture
- Rapid Reporter
- BB TestAssistant
- BB FlashBack Express
- CamStudio OpenSource
Another suggestion by Lisa Crispin for recording and showing bugs: Quicktime. From Srinivas Kadiyala we have a few additional suggestions: SnagIt , qSnap, Paint (PrintScreen). Lalit has let me know that QTrace is now qTestExplorer! Click here to learn more! And thank you Lalit for the correction! From Kobi Halperin we have Defect Scribe that he hopes to explore and share information about.
Keep the suggestions coming and I will update this page.
How are you gathering your Testing Artifacts?
Do you record your testing?
Do you use screen cap tools?
Or do you have another method to provide your Testing Artifacts?
As I have mentioned in a previous posting, I have a lot of admiration for Lalitkumar Bhamare and I was honored when he asked me for an interview for his excellent e-magazine. His interview provides some insight into my professional and personal life. So grab a cup of tea and perhaps a hot scone to not only read my interview but to also enjoy the wonderful articles written by Testers from around the world! My preference is loose Earl Grey Supreme by Harney and Sons. Speaking of scones… here is a great recipe for scones!
Click here for my interview.
Throughout the “What is Your Legacy” series, I have mostly focused on the Testers in the trenches and I hope you enjoyed learning more about Testers that you may not be connected. Perhaps you found one or more Testers that you will start following on Twitter or their blogs. I love how the Testing community supports one another and how we share information within the community. Today I would like to talk about the book “How to Reduce The Cost of Software Testing”.
This book was written by many Testers who responded to a couple of questions posted on LinkedIn. It is an amazing book filled with the collective knowledge of more than 20-Testers from around the world sharing their thoughts and experiences on reducing the cost of Software Testing while still identifying the problems and bugs. A brief bio is provided on each of the authors with most of them having active websites. This is another great way to “meet” more Testers within the community.
This book also introduced me to Testers such as Selena Delesie who wrote an important chapter on “The Cost of Quality”. She presents different processes and approaches to reduce costs while improving quality through a fictional company case study. I think most of us are challenged to reduce the cost of testing but retain a high level of quality testing. We need to understand that cost as we make decisions since there are typically many different paths to choose from.
Another Tester I learned about through this book was Catherine Powell who wrote a chapter called “Opportunity Cost of Testing”. I love this chapter because as Testers every decision we make has a cost. We may select one set of tests over another set based upon the requirements and known risks. Testers are always fighting the clock; therefore understanding the opportunity costs of our decisions is fairly important.
This book is packed with valuable information; a great way to get acquainted with a lot of Testers; and the chapters can be read in any order. It does not get much better than that! Hopefully you will have an opportunity to read this wonderful book and apply what you are learning to your own department.