Exploratory testing services

What is exploratory testing?

Exploratory testing is a test process where no specific scripted test scenarios are used. The testing team explores the product intuitively, learns from it and generates documentation as they go. Tests procedures are created when situation needing them are encountered while testing. Any verification performed by a QA team during an exploratory testing round is included in a file (excel sheet, mindmap, etc…) shared between all testers. This file summarizes every test that was made on the product, in order to reproduce and improve the testing round as the project evolves.

Why should you perform exploratory testing?

A common misconception about this type of testing is that it consists of a tester doing whatever he feels like with the product. This couldn’t be more incorrect. The advantage of doing exploratory testing is that it relies on humans’ biggest strength: their logic. While scripted tests are good and should be used during a complete QA process, exploratory testing helps finding edge cases that could have easily been missed when designing the test scripts. As they use the product like average users would, testers will quickly spot the vulnerable areas of the project and will instinctively try to dig deeper in such areas.

Another huge advantage of exploratory testing is that it can save a considerable amount of money. Rather than investing a big chunk of the QA budget into the creation of a test plan or of tests documentation of any sort, the money spent on exploratory testing is used for two purposes at once: Test and create documentation for future tests. While some people may argue that having a tester perform the testing and the design of the test documentation simultaneously will lower the quality of both tasks, it is the best way to get the ball rolling quickly. The return on investment can be extremely interesting, as it provides good documentation for the future without having to slow the development process.

Finally, the fact that exploratory testing has no specific order to follow in terms of use-cases considerably helps testers find important bugs faster. By not having to follow a specific user path (in case of a test plan driven QA round, for example), the tester will most likely explore sections that could have been left for the end of the tests on a scripted run. In the end, exploratory potentially helps finding bigger problems faster.

How can we help?

Our team is composed of professional testers, some of them having over 10 years of experience. They’ve done their share of exploratory testing in the past and they know how to do it properly and efficiently. Their experience made them learn where to dig in various types of projects and to quickly identify the high-risk areas.