How do you balance exploratory and scripted testing?

2 What is scripted testing?

Scripted testing is a type of testing that involves following a predefined set of steps, scenarios, or cases to test the software. You usually prepare the scripts before testing, based on the requirements, specifications, or design of the software. Scripted testing is often done by testers who have a detailed knowledge of the software's features, inputs, and outputs.

3 Why use exploratory testing?

Exploratory testing has several advantages in agile software development, such as the ability to test the software in a realistic and dynamic way, simulating how users would interact with it. This type of testing can also help uncover unexpected or hidden bugs, issues, or behaviors that scripted testing might miss. Additionally, exploratory testing enables you to adapt to changing requirements, feedback, or priorities and test the software as it evolves. Finally, it fosters collaboration, communication, and learning among the testers and other stakeholders as they share their findings, insights, and suggestions.

4 Why use scripted testing?

Scripted testing in agile software development has several advantages, including ensuring consistency and repeatability in testing, verifying the software meets criteria and works as intended, automating some or all of the testing process, and providing documentation, evidence, and metrics of the testing activities, results, and quality. Scripted testing can save time and resources, while also improving efficiency and reliability.

5 How to balance exploratory and scripted testing?

Finding the right balance between exploratory and scripted testing in agile projects is not a straightforward task. The optimal balance depends on various factors, such as the type, size, complexity, and maturity of the software, the goals and expectations of the testing, the time, budget, and resources available for testing, as well as the skills, experience, and preferences of the testers and other stakeholders. To help you find this balance, some general guidelines include using exploratory testing early and often in the development cycle to get feedback and identify risks; using scripted testing later and periodically to validate and verify the quality of the software; combining both types of testing in a complementary way to cover different aspects and perspectives; and adjusting the balance as needed based on feedback, data, and learning from the testing.

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?