Session notes that you use when you adopt an exploratory testing approach can be used to capture more than bugs. They not only serve as a memory of a bug, but a structured testing and learning method can be deduced from the session notes.
Exploratory software testing
In theory, we can consider software testing as a very rationale approach. You start from unit of code or requirements and then you create the tests that will prove that your software does what it is expected to do… and doesn’t create problems with edge cases. In his book Oblique Testing, Mike Talks propose to add an additional perspective to software testing using the oblique strategies approach.
The Exploratory Testing Chrome Extension is a free and open source extension for the Chrome browser that is designed to make exploratory testing of web sites easier. This extension will allow you to take notes during your exploratory testing sessions with a nice set of additional features.
TestInsane Technologies has created a repository of software testing mind maps. A mind map is a diagram used to visually organize information. It is often created around a single concept to which associated representations of ideas such as images, words and parts of words are added. Major ideas are connected directly to the central concept, and other ideas branch out from those.
TestNote.io is a free hosted application that provides simple note taking assistance for exploratory testing. You can record the actions, questions, ideas and bugs that arise during your software testing explorations and export them in different formats.
Exploratory testing is a concept of software testing where the tester combines application learning, test design and test execution in the same activity. This approach can showcase the results that a skilled tester can provide with manual tests. In this article, Kimberly A. Stockett provides three key approaches about how to change the attitudes of your software development team to adopt exploratory testing.
It’s commonly said that Test Automation means you need less testers on the team, it speeds up the testing process and allows more time for Exploratory Testing. In this talk Richard shares his critique of these common outcomes by calling upon his experiences of working in and managing teams where Automation has played a crucial part in the testing approach and has been used to great effect; but hasn’t resulted in the above outcomes.