How does change control affect test planning in an agile project?

Testers must stop all testing until the change is fully implemented

Testers must rewrite all test cases from scratch after every change

Testers must assess the impact of approved changes on existing test cases and adjust the test plan accordingly

Testers are not affected by changes because agile teams do not use change control

An agile team wants to adopt a configuration management tool that supports branching and merging for both code and test scripts, and also provides a way to link test cases to user stories. Which type of tool best fits this need?

A requirements management tool.

A continuous integration server.

A version control system such as Git.

A test management tool that integrates with a version control system.

In an agile project, what is the primary role of configuration management in supporting testing?

To automatically execute all regression tests whenever any code change is committed

To ensure that testers and developers are working with known, consistent versions of code, test assets, and environments

To define the test strategy and decide which test levels are needed for each iteration

To replace the need for test planning by providing a complete history of all changes

In agile testing, what is the purpose of change control?

To automate the execution of all tests whenever a change is made

To ensure that testers are notified of changes only after the release

To reject all changes that are not requested by the product owner

To manage and coordinate changes to configuration items so that their impact on testing is understood and addressed

A tester is working on a test script that is shared across multiple projects. The tester needs to make a change that will affect the script's behavior for all projects. What is the best practice for managing this change?

Use a branch in version control to make the change, then merge it back after review and testing.

Ask the project manager to approve the change before making it.

Create a copy of the script for each project and update only the copy for the current project.

Make the change directly in the shared script and notify all project teams.

Certified Tester Foundation Level Agile Tester

Domain 2Objective 4

Testing and Configuration Management CT-AT Practice Questions (Page 5)

Part of the Fundamental Agile Testing Principles, Practices, and Processes domain, which makes up ~44% of our current practice bank.

31questions here

7free pages

7concepts

Questions 21–25

21foundation · easy
How does change control affect test planning in an agile project?
Select an answer first
22application · medium
An agile team wants to adopt a configuration management tool that supports branching and merging for both code and test scripts, and also provides a way to link test cases to user stories. Which type of tool best fits this need?
Select an answer first
23foundation · easy
In an agile project, what is the primary role of configuration management in supporting testing?
Select an answer first
24foundation · easy
In agile testing, what is the purpose of change control?
Select an answer first
25application · medium
A tester is working on a test script that is shared across multiple projects. The tester needs to make a change that will affect the script's behavior for all projects. What is the best practice for managing this change?
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.