Changing Team Mindsets to Adopt Exploratory Testing
By: Kimberly A. Stockett
Exploratory testing is not a new concept, but it can be challenging to adopt properly because it requires a change in mindset for the whole project team. Everyone, from the project manager down, has to get on board with the process if you expect to get the best results. Implemented correctly, exploratory testing can enable teams to find defects earlier, it can empower testers and boost job satisfaction, and it can ultimately deliver a better product.
In order to get there, and reap those tantalizing rewards, it’s vital to look at three areas and set realistic expectations.
Project Development Team – Expect significant results earlier
There’s a reduction in documentation and less of a rigid structure to exploratory testing that can be alarming for the developers, project managers and business analysts. The important thing is to explain to them how the process works and make it clear that there is a formalized plan. Instead of writing test cases, testers will create workflow charters. There’s a shift from a clear step-by-step flow through functional testing to integration flows. With exploratory testing you get a combination, a holistic approach that generally leads to a much quicker identification of serious defects.
Instead of ticking off individual functions, exploratory testers are going to be looking at how functions connect and flow together. This approach reveals any gaps in the requirements much earlier than a traditional testing approach would. Coverage plans might be mind-maps, rather than traditional documents, and testers will use recording tools to capture sessions. Expect a learning curve, as the development team and the testers get to grips with the necessary tools, which are more visual and less detailed.
By fostering communication between testing and development, you can smooth the path to effective exploratory testing.
Testing Team – Expect to extend your thoughts
The testers also have to change their attitudes to be successful at exploratory testing. They need to be flexible, open to new ideas, willing to take risks, think outside the box, and examine in-depth. Instead of robotically sticking to test cases, they have the purview to go off-road when they see a potential issue developing, in order to get a better look.
With multiple testers there’s an emphasis on group evaluations over traditional lone wolf reviews. Testers have to draw up their own charters and decide what areas of the product to explore and test. They set their own expectations for coverage and stay adaptable. After each testing session, testers will get together and discuss what they found, set priorities, agree on defect severity, and evaluate where to focus for the next session.
Exploratory testing is about being proactive and taking responsibility for your own approach. They may have a general direction to focus on, but they’ll need to decide when to change tack, where to push, and what to explore. This freedom can take some getting used to, but controlling their own direction leads to a much greater, more thorough, understanding of the product being tested, and increased satisfaction in the results.
... to read more articles, visit http://sqa.fyicenter.com/art/