Free ASTQB sample questions

Correct answer: Integration Testing

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.

Correct answer: False

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.

Correct answers: Equivalence Partitioning; Boundary Value Analysis; Decision Table Testing

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.

Correct answer: Test Environment Setup

According to the flowchart, Test Environment Setup takes 8 days, which is the longest duration of any stage in the process. This represents the most significant delay and is therefore the primary bottleneck that the team should focus on improving.

Correct answer: To ensure the meeting proceeds efficiently, mediates disagreements, and fosters a collaborative environment.

This accurately describes the key responsibilities of a moderator. Their primary function is to lead the review, maintain focus, ensure the process is followed, and mediate any conflicts to help the team reach a consensus in a professional and constructive manner.

Correct answer: Novel or unexpected defects that fall outside the predefined test scripts may be missed.

This is the core risk. Automated tests are excellent at verifying known, expected behavior repeatedly. However, they can only check what they are programmed to check. Exploratory testing leverages human intelligence, curiosity, and domain knowledge to discover defects in unexpected scenarios that were not anticipated in the formal test scripts.

Correct answer: Absence-of-errors is a fallacy.

This principle directly addresses the scenario. It states that finding and fixing many defects does not guarantee success if the system built is unusable or does not fulfill the users' needs and expectations. The software may be functionally bug-free but still be the wrong product.

Correct answer: Adopt a risk-based approach prioritizing security testing of the MFA and secure messaging modules, followed by extensive usability testing with elderly users, and performance testing of critical patient record pages. Functional testing will be focused on complex scheduling rules.

This is the most effective strategy. It directly addresses the highest risks identified in the case study: security (HIPAA), usability (elderly users), and performance (responsiveness). By prioritizing testing efforts based on these risks, the team can use its limited budget to make the biggest impact on quality and compliance, while still validating complex functional areas.

Correct answer: To validate that the system is fit for use and meets the business requirements from the end-user's perspective.

This is the primary objective of Acceptance Testing (specifically, User Acceptance Testing or UAT). It is performed by business users to validate that the software meets their needs and is acceptable for deployment. In the V-model, this level corresponds to the initial requirements gathering phase.

Correct answer: Static testing, such as reviews of UI mockups and prototypes, is likely insufficient or being skipped.

This is the most plausible root cause. A high number of critical UI defects that block workflows suggests that fundamental design and usability issues are not being caught early. Effective static testing of UI/UX designs and requirements would identify such problems before any code is written, preventing them from becoming expensive defects in the final product.