Experience-based testing is the test design technique for which a document containing a classification of all the defects found during the system test phase and after the delivery in the production environment can be considered a test basis. Experience-based testing is a technique that relies on the knowledge and intuition of the testers to design and execute test cases based on their experience with similar systems, technologies, domains, or defects. A document containing a classification of all the defects found during the system test phase and after the delivery in the production environment can provide valuable information and insights for testers to identify potential defect-prone areas or scenarios and focus their testing efforts accordingly1 explains experience-based testing as follows:
Experience-based testing techniques are based on the tester’s experience, knowledge and intuition. These techniques leverage the tester’s skill in finding defects and designing tests that are effective in exposing failures. Experience-based testing techniques are often used when there is no or insufficient documentation available for the system under test, or when there is not enough time to apply more formal techniques.
Some examples of experience-based testing techniques are:
Error guessing: The tester uses their personal experience or intuition to guess what functionality might fail or cause errors, and designs test cases accordingly.
Exploratory testing: The tester simultaneously learns about the system, designs test cases, executes tests, and reports results, using an iterative and interactive approach.
Checklist-based testing: The tester uses a list of items or tasks that need to be verified or completed during testing, based on previous experience or best practices.
A, C, and D are incorrect answers. Structure-based testing, decision coverage testing, and specification-based testing are not test design techniques for which a document containing a classification of all the defects found during the system test phase and after the delivery in the production environment can be considered a test basis. Structure-based testing is a technique that uses the information of the internal structure of the component or system to derive test cases. Decision coverage testing is a type of structure-based testing that aims to cover all the possible outcomes of each decision in the code (true and false) at least once. Specification-based testing is a technique that uses the requirements and functionality of the system to derive test cases. These techniques require access to the source code or documentation of the system under test, which are not provided by a document containing a classification of all the defects found during the system test phase and after the delivery in the production environment.
