TA-5.2.2 K3 Apply
Apply a review technique to a test basis to find defects
A well-defined test basis serves as the cornerstone for ensuring the quality of work products and the success of projects. Reviewing the test basis helps identify and address defects early, preventing defects from escaping to subsequent phases.
The TA can employ various review techniques during the individual review to identify defects in the test basis. Selecting the most appropriate review technique can enhance the efficiency and effectiveness of the review. This selection should consider factors such as reviewing goals, project objectives, available resources, test basis type, associated risks, business domain, and company culture.
Below, this syllabus discusses five review techniques commonly used by the TA.
Ad hoc reviewing is carried out by reviewers informally, without a structured process. Reviewers are provided with little or no guidance on how the task should be performed. Ad hoc reviewing needs little preparation and is highly dependent on the reviewers’ skills. During the review, reviewers read the test basis and document the anomalies as they encounter them. This technique, left unmanaged, can lead to a high volume of duplicate anomaly reports from multiple reviewers.
Checklist-based reviewing involves evaluating the test basis against a predefined checklist. Checklists remind reviewers to check specific points and can de-personalize the review. Checklists can be generic or specific to quality characteristics, test objectives, or test basis type. The TA tailors the checklist to the test basis type, risk level, or test condition. This ensures that the review will focus on the most relevant aspects of the test basis. Checklists should be regularly updated with previously missed defects. Keeping checklists current prevents overlooking newly identified anomalies. Checklists are not all-inclusive. Therefore, the TA is not limited to checking the listed items. This maximizes defect detection and allows the TA to capture anomalies that checklists may not explicitly cover.
Scenario-based reviewing involves simulating a process or activity to identify anomalies and refine the test basis. This review technique is most effective when the test basis has a scenario-based format, such as a use case or activity diagram. In such cases, reviewers can perform "dry runs" based on the expected usage of the work product. Scenarios provide valuable guidelines, but the reviewers are not constrained to documented scenarios and should also think beyond the scenarios to identify more anomalies.
Role-based reviewing involves assigning specific roles or responsibilities to reviewers. Typical roles are based on specific end-user types (e.g., experienced, inexperienced, senior, or child user) or specific roles in the organization (e.g., administrator or regular user). Each role can be described by a persona (i.e., the concrete but fictional character designed to represent the characteristics, needs, goals, and preferences of a particular group of users). By distributing responsibilities among reviewers based on their roles, rolebased reviews allow individuals to focus on specific aspects of the test basis, ensuring comprehensive coverage and, at the same time, avoiding duplication of anomalies.
Perspective-based reading involves reviewing the test basis from various perspectives or viewpoints (e.g., designer, tester, marketer, administrator, and end user). This leads to more in-depth individual reviewing with less duplication of anomalies among reviewers. In addition, perspective-based reading requires the reviewers to attempt to use the test basis under review to generate the work product they would derive from it. For example, a tester would attempt to generate draft acceptance tests based on requirements specifications to see if all the necessary information is included.
The learning objectives explained by the sections found for this search, in the same order.
Apply a review technique to a test basis to find defects
None of the sections found for this search explains a learning objective.
No learning objectives match the current filters.
Business outcomes whose code or wording matches your search, with the learning objectives linked to each.
No business outcome matches this search.
No business outcomes match the current filters.
Keywords that the syllabi list at the start of a chapter — ISTQB Glossary keywords and domain-specific keywords — matching your search. Definitions are the ISTQB Glossary's.
No chapter keyword matches this search.
No keywords match the current filters.
Questions from the published sample exams that match your search — in the question, its answer options, or the objective or keyword it tests.
A company has developed an online shopping website. This year, to better serve new customers, the company decided to develop a new feature to guide new customers using the website. The requirements engineering team developed the following requirements for…
Match the review technique descriptions (1-4) with the correct technique names (A-D). Descriptions: 1. Reviewers simulate processes using use cases or activity diagrams and may explore beyond documented scenarios. 2. Reviewers use fictional personas (e.g.,…
No sample exam question matches this search.
No exam questions match the current filters.