scripted testing

The quality assurance process aims to make sure a software solution will operate correctly, without unexpected issues at the both development and release stages. A tester's main responsibility is to find even the smallest bugs which could negatively affect an application’s seamless work. In most cases, testers need to explore all the parts of an application: its functionality, interoperability, usability, visual appearance, etc. No wonder, sometimes the testing process is compared with the exploration of new lands. Both of them have similar roads: there is something unknown, and it’s the tester’s job to explore the lay of the land. That, in essence, is what Exploratory Testing is. Usually, it is done without any documentation, but with a clear and precise “Software cartography” which should include previous experience of the explorer and all the information about a product (its features, functionality, the business idea, etc). In this article, we’re going to look closer at this testing type to see its advantages and benefits in the process of quality assurance. Exploratory Testing: How it’s Done and Why it Matters Essentially, exploratory testing is a software testing approach which is executed without any previously developed documentation, test cases, or checklists. Therefore, a tester creates and runs tests based on his knowledge regarding the product. Overall experience and extensive technical background of QA engineers also play a big role, helping them execute tests more accurately. This testing type is convenient because a tester does not need to spend much time and energy creating test documentation. At the same time, the testing process is more intuitive and fast. The tester can determine at what stage the exploratory testing can be used to bring the greatest benefit, thereby mixing that with other testing types. This can be a solid step for a deeper understanding of the product. Thus, in the future, this will allow QAs to create more practical and useful tests. Finally, it could improve software not only from a technical but also from a business point. Exploratory testing includes many approaches. A tester can methodically reproduce real user behavior or perform a series of operations that a real user would never do. The goal is to just “explore” until you run into a bug, confusing UX, or a functionality error. Exploratory testing can also serve as a final check of software quality, helping QAs to determine potential weaknesses and failures ...

Exploratory testing is what James Bach called “scientific thinking in real-time”, “test design and test execution at the same time”.  Cem Kaner difines it as “sophisticated, thoughtful approach to ad hoc testing”. In other words, it is the opposite of scripted testing, which is about predefined test procedures carried out according to plan. When scripted tests are carried out and some information that offers a new test strategy comes up, it is the time for exploratory testing to reveal itself. It is especially useful in complicated situations when you don’t know much about the product and you have to prepare a set of scripting tests. Exploratory vs. Scripted Testing While scripted testing mechanizes the test process by writing down the scenarios and executing them, exploratory testing aims to exceed the bounds of this approach and make testing a more intellectually rich and fluid process. Scripted testing includes test cases and following them strictly. The steps are documented and the bugs are reported. This methodology can simply lead a tester to a desired result but many bugs users might face can fall out of scope. In this way you successfully solve certain issues and pass over the other ones. Exploratory tests are carried out ‘on the go’ and allow the tester to take steps which a user might take but not the ones the script tells. Having no restraints it shows how the product might be used ‘in the wild’. A common thing for the creators of the product is to miss some unexpected details. Exploratory testing brings a fresh eye here. In general, while scripted approach is a way of intensive testing of prescribed cases, the exploratory approach may uncover the unexpected defects. Pros And Cons Of Exploratory Testing Pros: No need for long preparation More intellectual approach Quick detection of bugs Does not require documentation Cons: Requires a certain mindset Its unstructured nature makes it easy to lose focus Due to performing ‘on-the-fly’ it can sometimes be difficult to define exactly which tests were run and hard to repeat certain cases if necessary When To Use Exploratory Testing You need to learn the product quickly and provide a rapid feedback You don’t know what the next test should be To diversify the testing process after having done scripts To do a brief check of other testers’ work Conclusion Exploratory and scripted testing are the two approaches that are not mutually ...