iSQI CTFL-AT - Certified Tester Foundation Level Agile Tester

The Test Pyramid is a model for organizing tests in a way to make the process of testing faster, efficient and cost-effective. This model focusses on getting maximum functional testing getting covered by faster and less brittle tests like Unit and API tests1. The main benefit of the Test Pyramid is that it helps in evaluating the amount of test cases needed for each level of testing. The Test Pyramid suggests that the number of test cases should decrease as we move up the pyramid, from unit tests to integration tests to end-to-end tests. This is because unit tests are more granular, isolated, and easy to write and maintain, while end-to-end tests are more complex, dependent, and brittle. The Test Pyramid also helps in balancing the test coverage and the test execution time, as unit tests provide high coverage and low execution time, while end-to-end tests provide low coverage and high execution time. By following the Test Pyramid, teams can optimize their testing efforts and resources, and ensure that they have a sufficient and effective test suite for their software. References: ISTQB® Foundation Level Agile Tester Syllabus, Section 2.2.1, page 16; ASTQB Agile Tester Certification Resources, Section 2.2.1, page 16; What is Test Pyramid : Getting started with Test Automation Pyramid, The Practical Test Pyramid - Martin Fowler, Testing Pyramid: What Is It and How To Use It | Solvd.

Comprehensive and Detailed Explanation From Exact Extract:

FromCTFL-AT Syllabus v4.0, Section 2.1:

"Acceptance criteria should be testable, meaning they should define expected behavior or measurable outcomes that can be verified."

Option Ais testable because it includesspecific, measurable conditions: response time, user load, and percentage of pages.

Option Bis vague aboutwhich vulnerabilitiesandhow errors are defined.

Option Cusessubjective language("clear and intuitive").

Option Dis vague about what "reasonable accuracy" means.

Comprehensive and Detailed Explanation From Exact Extract:

FromCTFL-AT Syllabus v4.0, Section 2.1Acceptance Criteria and Testability, acceptance tests must be directly related to thenew functionalitydescribed in the user story.

Option Dis correct — itvalidates the new featureof paying via smartcard credit, specificallyhandling edge cases(e.g., zero credit).

Option Ais incorrect —payment should failwith insufficient credit.

Option Bintroducesrequirements not mentionedin the story.

Option Ctestscredit card logic, not the new smartcard functionality.

 Equivalence partitioning is a black-box test design technique that divides the input domain of a system into classes of data from which test cases can be derived. The idea is that if a system works correctly for a representative value from an equivalence class, it will work correctly for all values from that class, and vice versa. Equivalence partitioning reduces the number of test cases by eliminating redundant ones. For the given user story, equivalence partitioning is the most suitable technique because it can test the different outcomes of the annual car tax calculation based on the power of the vehicle, which is the main input for the system. By testing one value from each partition, the tester can verify the functionality of the system and detect any errors in the calculation logic. The other techniques are not as suitable because they do not focus on the input domain of the system, but rather on the conditions, transitions, or scenarios that are not directly related to the user story. References:

: ISTQB® Foundation Level Agile Tester Syllabus, Version 2014, Section 2.2.2

: ASTQB Agile Tester Certification Resources, Agile Testing Foundations, Chapter 3, Section 3.2.2

: 3