An end-to-end test for an e-commerce site depends on a payment gateway that is sometimes slow and occasionally returns errors. The team is seeing intermittent test failures. What is the best way to handle this situation?

Increase the timeout values in the tests to avoid failures.

Remove the payment gateway from the test scope.

Treat the failures as defects and investigate the payment gateway integration.

Ignore the failures because they are due to the external system.

In an agile project, when is the most appropriate time to run end-to-end tests?

Only when a new external system is added

Only at the end of the project, after all features are complete

At the end of each iteration, on the integrated increment

Whenever the test environment is available

An agile team is working on a new feature that affects the order processing workflow. They want to incorporate end-to-end testing into their sprints without slowing down the release cycle. What is the most effective approach?

Skip end-to-end testing and rely on unit tests to catch all defects.

Perform manual end-to-end testing only when the feature is complete.

Run all end-to-end tests only at the end of the release cycle.

Automate critical end-to-end scenarios and run them in the continuous integration pipeline.

How can end-to-end testing be effectively incorporated into agile release cycles?

By creating a separate end-to-end testing phase after each release

By including end-to-end tests in the definition of done for each iteration

By running end-to-end tests only on the final release candidate

By delegating end-to-end testing to a separate team that runs tests independently

What is a common risk when end-to-end tests depend on external systems?

The external system will automatically adapt to test data

The external system will always be faster than the internal system

The external system may be unavailable or return unexpected data

The external system will provide a test environment for free

Certified Tester Advanced Level Agile Tester

Domain 1Objective 2

End-To-End Testing CTAL-AT Practice Questions (Page 1)

Part of the Test Strategy and Test Approach Challenges domain, which makes up ~20% of our current practice bank. ISTQB does not publish an official question count, but from its 90-minute exam (~35–60 total, ~7–12 in this domain), expect 2–3 from this objective — we provide 34 practice questions to prepare you well beyond it. (estimate)

34questions here

7free pages

8concepts

Questions 1–5

1expert · hard
An end-to-end test for an e-commerce site depends on a payment gateway that is sometimes slow and occasionally returns errors. The team is seeing intermittent test failures. What is the best way to handle this situation?
Select an answer first
2foundation · easy
In an agile project, when is the most appropriate time to run end-to-end tests?
Select an answer first
3application · medium
An agile team is working on a new feature that affects the order processing workflow. They want to incorporate end-to-end testing into their sprints without slowing down the release cycle. What is the most effective approach?
Select an answer first
4foundation · easy
How can end-to-end testing be effectively incorporated into agile release cycles?
Select an answer first
5foundation · easy
What is a common risk when end-to-end tests depend on external systems?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CTAL-AT

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by ISTQB. “CTAL-AT” is a trademark of its owner, used for identification only.