ASTQB Practice Questions

This is the correct purpose. Exit criteria are a set of predefined and agreed-upon conditions that must be achieved to conclude a test activity. Examples include reaching a certain level of code coverage, having no outstanding critical defects, or passing a specific percentage of test cases.

There are two IF statements, each with a TRUE and a FALSE branch, totaling four branches. We need to cover all four outcomes.
Case 1: OrderValue > 100 is TRUE (e.g., 120). Let IsPremiumMember = FALSE. This covers the first TRUE branch.
Case 2: IsPremiumMember = TRUE (e.g., TRUE). Let OrderValue = 50. This covers the second TRUE branch.
Case 3: Both conditions are FALSE. OrderValue <= 100 (e.g., 50) and IsPremiumMember = FALSE. This covers both FALSE branches simultaneously.
Therefore, a minimum of 3 test cases can achieve 100% branch coverage.

This is the ideal stage. After the code is successfully built and deployed to a stable, production-like environment (staging), the automated regression suite can run. This validates that the new changes have not broken existing functionality before the code is considered for promotion to production.

This is a core principle of risk-based testing. When time is limited, prioritizing test activities based on the likelihood and impact of potential failures ensures that the most important areas receive the most attention.

Adding skilled resources, if they can be onboarded quickly, can help increase the amount of testing that can be accomplished in the remaining time. This directly addresses the resource constraint.

This is an effective project-level mitigation. By reducing the scope of the release, the amount of testing required is also reduced, allowing the team to focus on ensuring the quality of the remaining high-priority features.

This is correct. Professional exploratory testing is structured through techniques like session-based test management, where testers work with specific charters (missions), use time-boxing, and document their findings, notes, and issues. It combines simultaneous learning, test design, and test execution in a structured way.

This is the correct application of equivalence partitioning. For a 'Silver' member, the two partitions are purchases up to $75 (no discount) and purchases over $75 (discount applies). Choosing one representative value from each partition ($65 and $85) is the most efficient way to test this logic using this technique.

This is the best choice for an Agile context. A burn-down chart provides a clear visual of progress against the sprint goal. Highlighting blocking issues and critical defects is crucial for the team to address impediments quickly, which is a key focus of daily stand-ups and sprint reviews.

This is a classic example of integration testing. It specifically focuses on testing the interface and interaction between two separate software components or services ('User Authentication' and 'Order Processing') to ensure they work together as expected.

This is correct. The pesticide paradox states that if the same tests are repeated over and over again, they will eventually no longer find new defects. To overcome this, test cases need to be regularly reviewed and revised, and new tests need to be written to exercise different parts of the software.

Equivalence Partitioning is highly effective here for dividing the possible inputs into groups that are expected to be processed similarly. For example, ages 18-25 might be one partition, and 26-40 another. This helps achieve broad coverage efficiently.

Boundary Value Analysis is crucial for testing the edges of the numerical ranges, such as ages 18 and 65, and the number of violations (0 and 5). Errors often occur at these boundaries, making this technique essential.

Decision Table Testing is ideal for this scenario because it involves complex business rules based on combinations of different conditions (age, violations, vehicle type). This technique systematically covers all valid combinations of rules, ensuring no logic path is missed.