ISTQB CTAL-ATT Practice Questions with Explanations
Free ISTQB CTAL-ATT practice questions. 11 of them, each with the correct answer, a full explanation, and the reason every other option is wrong.
CTAL-ATT practice questions
Question 1
Which requirements engineering technique would BEST identify how different groups of users may interact with a system, helping to identify gaps and inconsistencies in a user story?
- A. Storyboards
- B. Story Mapping
- C. Personas
- D. Use Cases
Show answer and explanation ▾
Correct answer: C
Personas describe typical users and how each group would interact with the system, which exposes gaps and inconsistencies in a user story from different user viewpoints.
Why the other options are wrong:
- A. Storyboards show a sequence of interactions but not the range of user groups.
- B. Story mapping organises stories along the user journey and does not model different user groups.
- D. Use cases describe the interaction between an actor and the system for a goal, rather than characterising different groups of users.
Question 2
You are an experienced tester on an Agile team that is producing a new application. The product backlog has been refined sufficiently to begin development for the first release.
This stories in the backlog contain a mixture of functional and non-functional requirements, as well as some technical stories that will provide elements of the application’s infrastructure.
The developers have decided to use TDD as a development approach but automation of the acceptance tests is not yet planned.
You have been asked to recommend whether or not the team should take an ATDD approach as well as TDD.
What would be the BEST recommendation in these circumstances?
- A. NO, do not use ATDD, because it is not compatible with the developers’ TDD approach.
- B. YES, use ATTD, but for the functional requirements only because it cannot be applied to non-functional or technical requirements.
- C. YES, use ATTD for all requirements including non-functional and technical stories.
- D. NO, do not use ATDD, because it will not work when the acceptance tests are not automated.
Show answer and explanation ▾
Correct answer: C
ATDD can be used for all kinds of requirements, including non-functional and technical stories, and it sits alongside developer TDD. The acceptance tests do not have to be automated to gain the benefit of agreeing criteria up front.
Why the other options are wrong:
- A. ATDD and TDD are compatible and are often used together.
- B. ATDD is not limited to functional requirements.
- D. ATDD works even when the acceptance tests are not automated yet.
Question 3
You need to implement a Java class that validates a password entry field. The validation criteria states that the password must:
1. be a minimum of 8 characters.
2. contain at least one special character.
You are focusing on validation criterion 1 and have written a test class that checks that a 7 character password entry will fail validation.
You have written code designed to make this test class pass, however, on first execution of the test class it has failed.
What should you do next?
- A. Develop a test class with a 9 character password containing one special character and re-execute the code.
- B. Refactor the failing code to improve its design and structure.
- C. Repair the failing code and re-execute it for the test class.
- D. Add code to cover special character validation criterion 2.
Show answer and explanation ▾
Correct answer: C
In test-driven development a failing test after you write the code means the code is not yet right, so the next step is to repair the code and run the test again. Refactoring and new criteria only come after the test passes.
Why the other options are wrong:
- A. A new test with a different input does not fix why the existing test fails.
- B. Refactoring is done once the test passes, not while it is failing.
- D. New criteria are tackled only after the current criterion's test passes.
Question 4
The following user story has been written for a new application being developed to pre-book a space at a National Car Park. As a vehicle driver I want to be able to pre-book a car parking space online, selecting a disabled driver's space if needed So that I can pay in advance and receive confirmation of my parking space number. The following acceptance criteria have also been written: Payment can be made via PayPal, Debit or Credit Card. Confirmation of payment and car parking details should be sent after the booking process is completed. Driver information is stored in the reservation database. The database has been built and tested in a previous sprint, but the interface to the different payment methods have yet to be developed. As a tester in an agile team, you have been asked to review the user story. You have detected some issues with this story: It needs to cater for different user groups: a driver or disabled driver. It needs to cater for different vehicle types: a car, 4x4, van or motorbike. There are no acceptance criteria relating to how quick the booking process should be. How confirmation is to be sent for payment and space number, and other important details, have not been specified. A stub will be needed to test the payment method. Which pair of requirements engineering techniques are you MOST LIKELY to have used to uncover these issues?
- A. Storyboards and Personas
- B. Personas and Diagrams
- C. Diagrams and Story Mapping
- D. Story Mapping and Use Cases
Show answer and explanation ▾
Correct answer: B
Personas describe the different kinds of users, which exposes the missing user groups, vehicle types and their expectations such as booking speed. Diagrams of the booking flow and its interfaces expose the unspecified confirmation step and the undeveloped payment interface that needs a stub.
Why the other options are wrong:
- A. Storyboards visualize a sequence of screens or steps and would not reveal the missing payment interface or the need for a stub.
- C. Story mapping arranges stories to show scope and priority and would not surface the different user groups and vehicle types.
- D. Story mapping and use cases do not focus on the different types of users the way personas do.
Question 5
The following User story is being developed using the BDD approach:
As a Purchasing Manager
I want to see a list of all Purchase Orders placed so far this month with their total value So that I can control the amount of money being spent.
Which scenario is BOTH written in correct Gherkin format AND is appropriate for this User Story?
- A. Given that three Purchase Orders with a total value of £21.75 have been placed so far this month, When the Purchasing Manager requests the list of Purchase Orders placed this month, Then the 3 orders and their total value of £21.75 are displayed.
- B. Given that I am a Purchasing Manager AND three Purchase Orders with a total value of £21.75 have been placed so far this month, When I request the list of Purchase Orders placed this month, Then all orders and their total value of £21.75 are displayed
- C. Given that three Purchase Orders with a total value of £21.75 have been placed so far this month AND the Purchasing Manager has navigated to the Purchase Order Reporting page, When the Purchasing Manager clicks the button “List of Purchase Orders placed this month”, Then the 3 orders and their total value of £21.75 are displayed.
- D. Given that three Purchase Orders with a total value of £21.75 have been placed so far this month, When the Purchasing Manager requests the list of Purchase Orders placed this month, Then the appropriate details are displayed.
Show answer and explanation ▾
Correct answer: A
This scenario has one precondition, one action and one outcome that can be checked exactly: three orders and a total of 21.75. It describes behavior in business terms, without user interface detail, and it matches what the Purchasing Manager wants from the story.
Why the other options are wrong:
- B. It expects all orders to be displayed without stating how many, so the result is not precisely checkable.
- C. It ties the scenario to page navigation and a specific button, which is implementation detail rather than behavior.
- D. Its outcome, that appropriate details are displayed, cannot be verified because it names no expected values.
Question 6
Your Agile team is developing a web-based system that will allow users to browse and buy online from a store’s shopping catalogue.
Continuous Integration has been implemented and technically it is working well, running several times per day, but each run is taking almost as much time as the team is prepared to allow.
It is clear that after a few more iterations, as the number of tests needed grows with the product, it will be taking too much time.
Which of the four options contains a pair of solutions that will BOTH help to solve this problem?
Only include unit and component integration tests in the automated CI runs.
Schedule low priority tests to be the first ones executed in each run, in order to provide rapid build verification.
Reduce the extent to which the automated tests go through the user interface, using technical interfaces instead.
Reduce the number of CI cycles run each day.
Select a subset of automated tests for the daytime CI runs, and run as many of the other tests as possible in an overnight cycle.
- A. c and e
- B. a and c
- C. b and d
- D. d and e
Show answer and explanation ▾
Correct answer: A
Tests that use technical interfaces instead of the user interface run much faster, and moving part of the suite to an overnight cycle shortens the daytime runs while still executing the remaining tests. Both changes cut run time without giving up coverage or feedback.
Why the other options are wrong:
- B. Limiting CI runs to unit and component integration tests drops the higher-level tests from CI altogether.
- C. Running low priority tests first delays the most valuable feedback, and fewer CI cycles does not shorten a run.
- D. Reducing the number of CI cycles per day does not make each run faster and slows feedback to the team.
Question 7
Your team is developing an e-shop application (the SUT) that will use a third-party service to process payments via an API. This third-party payment gateway is itself still under development.
Which statement contains a pair of benefits that can BOTH be expected from service virtualization in this circumstance?
- A. Earlier testing of the API; reduction in the amount of test data needed.
- B. Earlier discovery of defects in the SUT; the ability to share code between the SUT and the payment gateway.
- C. Parallel compilation, continuous integration, and test automation; more effective configuration management.
- D. Realistic testing of the SUT before the actual payment gateway is available; simplification of the test environment.
Show answer and explanation ▾
Correct answer: D
A virtual service simulates the unfinished payment gateway, so the e-shop can be tested against realistic responses before the real gateway exists. It also simplifies the test environment, because no real third-party system has to be set up and maintained.
Why the other options are wrong:
- A. Service virtualization does not reduce the amount of test data needed.
- B. Service virtualization does not let the SUT and the payment gateway share code.
- C. Parallel compilation and configuration management are not benefits of service virtualization.
Question 8
You are part of an agile team creating a user story.
Which of the following requirements engineering techniques would you use to provide a visual representation of the system and help to see the ‘overall’ story with the functional flow?
- A. Storyboards
- B. Story Mapping
- C. Personas
- D. Use Cases
Show answer and explanation ▾
Correct answer: B
Story mapping lays user stories out in two dimensions along the user's flow through the system. That gives a visual overview of the whole product and its functional flow, so the team can see the overall story.
Why the other options are wrong:
- A. Storyboards illustrate a single scenario or sequence of screens, not the overall functional flow of the system.
- C. Personas describe types of users, not the functional flow of the system.
- D. Use cases describe individual interactions between an actor and the system, mostly as text.
Question 9
You have identified existing test cases that require re-factoring.
Which is the NEXT task you should perform?
- A. Re-run the tests to ensure that the test results remain the same.
- B. Analyze the impact of the functionality of the current iteration on the existing regression tests.
- C. Make changes to the internal structure of the tests to improve maintainability.
- D. Adjust the observable behaviour of the tests to meet the user stories.
Show answer and explanation ▾
Correct answer: C
Once the tests that need refactoring are identified, the refactoring itself follows: the internal structure of the tests is changed to make them easier to maintain, without changing what they verify. Re-running the tests comes after that.
Why the other options are wrong:
- A. Re-running the tests comes after they have been refactored, to confirm the results are unchanged.
- B. This analysis is what reveals which tests need refactoring, so it comes before identification, not after it.
- D. Refactoring must not change the observable behavior of the tests.
Question 10
Which statement about test automation is TRUE?
- A. Increasing test automation levels to increase the frequency of continuous deployment should always be an objective.
- B. Increasing test automation levels may decrease the frequency at which continuous deployments to production can be made.
- C. Minimizing the test suite by selecting, preparing and running only a subset of tests by using risk analysis should always be an objective.
- D. Increasing test automation levels will eliminate the need for manual testing during continuous deployment.
Show answer and explanation ▾
Correct answer: B
More automated tests take more time to build, maintain and execute. As the automated suite grows, each pipeline run takes longer, which can reduce how often deployments to production can be made.
Why the other options are wrong:
- A. The right level of automation depends on context, so raising it is not always an objective.
- C. Running a risk-based subset is one option that suits some contexts, not something that should always be the objective.
- D. Automation does not remove the need for manual testing such as exploratory testing.
Question 11
Which statement correctly describes continuous testing?
- A. Each new build of the system triggers a pre-defined set of tests to be executed automatically.
- B. Each modification made to the system triggers the tests that cover that change to be executed automatically.
- C. Each modification made to the system is automatically tested and then automatically made implemented in live.
- D. Each new build of the system triggers deployment into a testing environment.
Show answer and explanation ▾
Correct answer: A
In continuous testing, every new build automatically triggers a pre-defined set of tests, so the team gets fast feedback on each build without anyone starting the tests by hand.
Why the other options are wrong:
- B. Continuous testing runs a pre-defined set of tests on each build, not only the tests that cover one change.
- C. Automatically putting each tested change into live use describes continuous deployment.
- D. Deploying each build into a testing environment is a deployment step, not the testing itself.
That was 11 of 39.
The full ISTQB CTAL-ATT pack has all 39 questions, each with the answer, the explanation and why the other options are wrong, plus a questions-only copy for timed runs. $39.00 USD, paid once, with free monthly updates and a pass-or-your-money-back guarantee.
Get the full packNot ready yet? Get the first 13 free as one PDF by email. Get the Half Pack →
About the CTAL-ATT exam
These 11 ISTQB CTAL-ATT questions are free here. The free PDF has 13, free by email.
They are drawn from the same bank as the full CTAL-ATT pack, which has 39 questions in total.