Choose the Appropriate Test Method
Understand the Different Methods
Test methods are a bit like kitchen utensils.
To cook pasta, you might use a saucepan or a frying pan. Both could work, but one is clearly more efficient and gives you a better chance of success.
Testing methods work the same way. You’ll have a whole set of tools at your disposal, and it’s up to you to choose the right one at the right time.
In this chapter, we won’t cover every method that exists only those you’ll use most often:
Black-Box Testing
What does it involve?
This method verifies that the Product’s features work without worrying about how they are implemented.
In simple terms, you don’t know the source code, the design, or even the internal structure of the system. Imagine using a box without knowing what happens inside it.
What’s the Goal?
It lets you observe behavior from an end-user’s perspective and use the application as a real customer would.
You focus on inputs and outputs—not on how the system processes the data.
Advantages and disadvantages
Advantages include not needing any information about the application’s internal implementation, as the technical view is ignored.
Another advantage: this method is guided by the test plan, which gives you a clear procedure to follow.
The downside? Designing and running these tests can be time-consuming and costly.
Best practices
Determine the right test cases and avoid duplicate ones.
Duplication happens easily because no single test case will perfectly match your Needs. When writing test cases, make them adaptable so you can reuse them in future campaigns.
Exploratory Testing
What does it involve?
This method relies on exploration and the tester’s intuition to uncover bugs. Think of putting yourself in the shoes of a typical user.
Unlike functional testing, this approach is informal. You won’t have a test plan to follow step by step.
What’s the Goal?
To find defects that may not be detected using other methods.
It is often used for complex features or to check the user experience.
Example: You add a product to the shopping cart and navigate back and forth between the home page, the cart, and various product categories. You may use the site’s interface, browser functions, or even manipulate the URL.
Advantages and disadvantages
Main advantages: greater flexibility and the ability to adapt quickly to new specifications. It also complements other testing methods.
Disadvantages: it lacks traceability because nothing is planned in advance, and coverage may be insufficient if used alone.
Best practices
Define a clear goal: Before starting, identify what you want to explore.
E.g.: I want to test the shopping cart functionality.
Set a time limit: This method can be very time-consuming, so limit your sessions.
E.g.: I allow myself one 30-minute exploratory session per day.
Take detailed notes: Document your actions and results thoroughly.
You’ll thank yourself later when reporting steps to reproduce defects.
You may use session-recording tools (e.g., screen recorders)—but check whether this is allowed beforehand.
Non-regression testing
What does it involve?
This method ensures that features not impacted by the project continue to function as before.
What’s the Goal?
To ensure that changes in the software have not introduced new bugs into previously working features.
Advantages and disadvantages
These tests are generally executed after functional testing.
With each delivery, the non-regression tests you’ve identified must be run to ensure no unintended side-effects have been introduced.
Be vigilant when running these tests.
They can also be automated.
On the other hand, you do not need to test the entire non-impacted Scope!
Focus “only” on the areas of the application that might be affected by new features.
Best practices
Identify critical tests—non-regression should focus on mission-critical features.
Schedule these tests regularly (e.g., after each delivery).
Monitor results; if a test fails, investigate the cause via a defect report.
Automated testing
What does it involve?
These tests are executed by automated scripts developed by humans. They run predefined scenarios to test application features.
What’s the Goal?
To run tests quickly, reliably, and repeatedly, so issues are detected early and software stability is maintained.
Advantages and disadvantages
They save valuable time by running tests you no longer need to execute manually. This reduces project costs and provides better test coverage.
However, automation has a high initial cost. The investment in automation strategy and development can be expensive. This is why it’s crucial to clearly define your needs before automating.
Best practices
Automate non-regression tests, and maintain them whenever changes occur along those paths.
Choose Your Test Methods
Understand the test objectives: What am I trying to achieve?
Error detection?
Improving product quality?
Covering all scenarios?
Validating the user experience?
Identify available methods: What do I have at my disposal?
Is manual testing possible?
What automated test assets do I have? Do they need updating?
Would exploratory testing add value?
Analyze requirements and project constraints: What am I allowed or able to do?
What time and resources will be available during the campaign?
How complex is the system?
What is the testing team’s skill level?
Stay flexible:
Adapt your choices as the project evolves.
Projects change during execution—reassess your decisions and avoid staying rigid.
In short, evaluate your scenarios, the test environment, and the tools available. This will help you understand how constraints interact—and highlight methods that will make your work easier.
Over to You!
Context
Your testing Scope is becoming clearer the “What.” Now it’s time to choose “How” to test the scenarios you defined.
Edouard has informed you that the technical resources who could develop or update automated test scripts will not be available before the test campaign begins.
Instructions
Identify the testing methods best suited to the situation, and justify your choices.
Summary
Test methods help you choose the most appropriate techniques to achieve your goals during the test campaign.
The 4 most common methods you’ll encounter are:
black-box (functional) testing, where you test without any knowledge of the code;
exploratory testing, used informally or when time is limited;
non-regression testing, to ensure non-impacted features still work;
automated testing, to automatically execute scenarios (such as non-regression tests).
Choosing test methods depends on your planned scenarios, environmental constraints, and the available methods.
If test methods are the utensils for cooking your test campaign, let’s move on to the ingredients by selecting the Resources you’ll need.
