When software testers or dedicated testing teams perform independent testing, they inevitably use test design. What is this?
Test design – is the stage in the process of software testing service, based on which test cases are designed in accordance with the previously defined quality criteria and test goals.
Roles of Responsible for Test Design:
- Test Analyst – defines “WHAT to test?”
- Test Designer – defines “HOW to test?”
- Test Designer – defines “HOW to test?”
Test Design Techniques:
- Equivalence Partitioning. As an example, you have the range of valid values from 1 to 10, and you must choose the correct value within an interval of, let’s say 5, and one wrong value outside the interval - 0.
- Boundary Value Analysis. The given analysis can be applied to fields, records, files, or to any kind of entities with limitations.
- Cause/Effect. It’s, as a rule, the input of combinations of requirements (causes) in order to get the system response (effect).
- Error Guessing. It’s when test analyst uses his/her knowledge and skills for interpreting the specifications in order to “predict” the system crash caused by some input conditions.
- Exhaustive Testing – it is an extreme case. Within this technique, you must check all the possible combinations of input values, and it should find any problems. In practice, this method is not possible, due to the vast amount of input values.
- Treceability Matrix - is a two-dimensional table, which contains the corresponded functional requirements of the product and prepared test cases. The given technique is used by QA engineers to validate the product tests coverage.
Posts
