In test-driven development (TDD), which of the following is the correct sequence of steps?

Write a failing test, write the minimum code to pass the test, refactor

Write production code, write a test, refactor

Write a test, refactor, write production code

Write production code, refactor, write a test

During a sprint retrospective, the team identifies that they often discover defects late in the sprint, leading to rework and missed commitments. Which practice should they adopt to catch defects earlier?

Implement continuous integration with automated tests

Delay testing until the end of the sprint

Assign a dedicated tester to the team

Increase the length of the sprint to allow more time for testing

A team is using a burndown chart to track sprint progress. Midway through the sprint, the burndown chart shows that the remaining work has increased instead of decreased. What is the most likely cause and what should the team do?

The team is doing too much testing; they should reduce testing to speed up

The team is not working fast enough; they should work overtime to get back on track

The team added new work to the sprint; they should discuss with the product owner whether to remove other work or adjust the sprint goal

The burndown chart is inaccurate; they should ignore it

Certified Tester Foundation Level Agile Tester

Domain 1Objective 4

Agile Software Development Approaches CT-AT Practice Questions (Page 1)

Part of the Agile Software Development domain, which makes up ~37% of our current practice bank.

30questions here

6free pages

8concepts

Questions 1–5

1foundation · easy
In test-driven development (TDD), which of the following is the correct sequence of steps?
Select an answer first
2application · medium
A team wants to ensure that all code changes are integrated and tested frequently to detect integration issues early. They currently have a manual build process that runs only at the end of each sprint. Which practice should they implement?
Select an answer first
3application · medium
During a sprint retrospective, the team identifies that they often discover defects late in the sprint, leading to rework and missed commitments. Which practice should they adopt to catch defects earlier?
Select an answer first
4expert · hard
A team is using a burndown chart to track sprint progress. Midway through the sprint, the burndown chart shows that the remaining work has increased instead of decreased. What is the most likely cause and what should the team do?
Select an answer first
5foundation · easy
Which scaling framework is designed to apply Scrum principles to large-scale projects with minimal additional roles and processes, essentially 'Scrum at scale'?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CT-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. “CT-AT” is a trademark of its owner, used for identification only.

Agile Software Development Approaches CT-AT Practice Questions (Page 1)

Questions 1–5

In test-driven development (TDD), which of the following is the correct sequence of steps?

A team wants to ensure that all code changes are integrated and tested frequently to detect integration issues early. They currently have a manual build process that runs only at the end of each sprint. Which practice should they implement?

During a sprint retrospective, the team identifies that they often discover defects late in the sprint, leading to rework and missed commitments. Which practice should they adopt to catch defects earlier?

A team is using a burndown chart to track sprint progress. Midway through the sprint, the burndown chart shows that the remaining work has increased instead of decreased. What is the most likely cause and what should the team do?

Which scaling framework is designed to apply Scrum principles to large-scale projects with minimal additional roles and processes, essentially 'Scrum at scale'?

Keep studying — Agile Software Development