Last weeks Exploratory Testing webinar titled ‘Exploratory Testing with JIRA’ was very well-attended with over 800 people joining us to learn about the what, why and how for using Exploratory testing. Below you can view the on-demand version of the webinar, the slides and read a handful of my key takeaways.
Exploratory Testing should be focused on the product, and those involved should have knowledge about the ins and outs of the product, and how it is tested.
Exploratory Testing is not just for testers. Developers are, and should be, encouraged to get involved in the testing process.
Why use Exploratory Testing? Exploratory Testing can save up to seven times the amount of time spent in traditional testing. More bugs and defects are typically found, and results from tests are more accurate.
Exploratory Testing allows for flexibility in how bugs and defects are found, and can find them more effectively than can be found in traditional testing. ET also prioritizes documentation and following plans for end results. There is a priority on making sure all problems are documented and everything can be explained, and nothing is done by responding to a change.
Exploratory Testing leads to better job satisfaction, more critical thinking, and it is easier to move from tester to SME. It also is easier to transfer knowledge to other teammates, and reading comments becomes less of a tedious affair.
Exploratory Testing should foster a knowledge repository, and foster communication of knowledge with those in the organization.
Session reports are common, and are suggested, for Exploratory Testing. Several methods are common, like Session Based Test Management, and PROOF.
Sign up for our next webinar and view other on-demand recordings in our resource center.