CTAL-ATT Exam Questions Tutorials

Table 2 provides the best test coverage because it includes tests for adding a non-existent member (Member4), which should result in an error, and it also tests for removing a member and then deleting the group, which is the correct sequence of actions according to the requirements. The other tables either do not test all the required scenarios or have actions in thewrong order (e.g., attempting to delete the group before removing all members). References = ISTQB Advanced Level Agile Technical Tester documents and Training resources.

The correct sequence when refactoring test cases in an Agile project is to first identify the test cases that need refactoring. Following identification, an analysis is conducted to understand the changes needed. After analysis, the actual refactoring of the test case is done. Once refactored, the test cases are re-run to ensure they work as expected. Finally, an evaluation is performed to confirm that the refactoring has improved the test cases and that they meet the required standards.

References = The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of refactoring test cases in Agile projects and provides a practical task-list for refactoring test cases123.

In Behavior-Driven Development (BDD), scenarios are formulated to describe the general behavior of the system from the perspective of a specific user. This helps in understanding the user’s needs and how the system should respond. It’s important for scenarios to be clear and understandable to all stakeholders, including non-technical ones, which is why they are often written in simple language describing the behavior rather than the technical actions.

 Option D is written in correct Gherkin format and is appropriate for the User Story. It clearly states the precondition (three Purchase Orders with a total value of £21.75 have been placed), the action taken by the Purchasing Manager (requesting the list of Purchase Orders placed this month), and the expected outcome (the 3 orders and their total value of £21.75 are displayed). This scenario directly addresses the Purchasing Manager’s desire to see a list of all Purchase Orders placed so far this month with their total value, which aligns with the User Story’s goal of controlling the amount of money being spent.

References = ISTQB Advanced Level Agile Technical Tester documents and Training resources12.