Test Design Techniques – Chapter 4 – ISTQB Foundation
ISTQB certification foundation level exam should not be challenging. This is the fourth part of a summary series to help you memorize what will most likely be on the ISTQB exam questions.
Read, then practice the exam for chapter 4 – Test Design Techniques, link at the end of this summary and practice the quiz as much as you like or until you feel comfortable enough to go to the next chapter.
If you feel that you are ok to try the actual exam, there’s a quiz for that as well next to chapter five.
The more you read, the more you understand, and the more you know more you are ready to sit for the exam.
I have uploaded a mind map with a graphical visualization of the ISTQB Foundation Level topics, a kind of Cheat Cheat; you may find it helpful to help you with the exam.
I hope you like it. Feel free to drop me a comment, or inform anything that I’ve missed here. Good luck.
An item or event of a component or system that one or more test cases could verify.
A set of input values, execution preconditions, expected results, and execution postconditions, such as to exercise a part of the code.
Test procedure specification
A sequence of actions for the execution of a test.
Reasons to know test coverage
- Provide a quantitative measure of the quality of testing that has been done. It provides a way of estimating how much more testing is needed.
Three categories of test case design techniques
- Black box techniques
- White box techniques
- Experience-based techniques
Black box testing – test cases derived directly from a specification or a model of a system or proposed system (documentation).
Five types of specification-based techniques
- Equivalence partitioning
- Boundary value analysis
- Decision table testing
- State transition testing
- Use case testing
Reduces the number of tests needed by considering partitions are the only test cases required.
Boundary value analysis
Look for tests that focus on the possible boundaries of inputs, noting that most errors occur there.
Decision table testing
It uses a table to list out all possible inputs and actions that can arise to ensure each is tested.
State transition testing
It uses a state diagram to list all the possible states and transitions that can occur to ensure each is tested.
Use case testing
Capturing individual interactions between actors and the system to help test specific scenarios that are likely to be performed.
White box techniques – are used to explore the system or component structures.
Testing aimed at exercising programming statements.
Testing is aimed to ensure that the decisions in a program are adequately exercised.
Techniques that you fall back on when there is no adequate specification or no time to run the full set of tests.
It uses the tester’s skill, intuition, and experience to identify special tests not easily captured otherwise.