Get your license!
Tool support for collaborative Exploratory Testing
The term Exploratory Testing is undoubtedly well known in tester communities. And perhaps you have tried it yourself because exploratory testing can be a lot of fun! No scripts to follow, just get started, explore, document, find potential bugs, and explore even more — no waisting of time with unnecessary structures and standards.
But what did your work look like? Did you end up with lots of notes? And after a break, did you not remember exactly where you stopped? And if you did an exploratory test in a team: what were your colleagues working on, and what were their results?
That's all over now! TestBench Cloud Services now offers comprehensive tool support for the entire process of collaborative Exploratory Testing. All information is quickly recorded in one place.
A timebox - called a session - is defined, which helps a team to synchronize and to focus — exploring, testing, and so on is done during the session.
A mission is defined, which describes for all team members what is the common overall purpose for the session. It should tell the testers why the session is done and what we hope to achieve, on an elevated level.
Individual objectives, test ideas, or agendas are described in test charters. Some or all charters may be needed to be carried out to achieve the mission. Thus, a tester may, during an exploratory test session, pick one or more charters and work based on them. Charters can be prepared before the session, and ideas for new charters come up during the session. To make sure that all necessary charters have been considered, or if some testers have special skills or knowledge needed for a specific charter, the organizer of an exploratory test session can decide to assign charters to individual testers.
During the session, testers do their exploratory testing, use charters, and document what they do or find in notes.
After the session, the team will do a debrief. In the debrief, the team and the organizer discuss the results, find agreement on what is a bug and what is not, and decide about the next steps.