Try our Free Demo Practice Tests for Comprehensive CTFL4 Exam Preparation

Traceability between test basis items and the test cases designed to cover them, makes it possible to determine which test basis items have been covered by the executed test cases.

Traceability between test basis items and the test cases designed to cover them, enables experience-based test techniques to be applied

Traceability between test basis items and the test cases designed to cover them, enables identification of which test cases will be affected by changes to the test basis items.

Traceability can be established and maintained through all the test documentation for a given test level, such as from test conditions through test cases to test scripts.

Configuration management helps reduce testing effort by identifying a manageable number of test environment configurations in which to test the software, out of all possible configurations of the environment in which the software will be released

Configuration management is an administrative discipline that includes change control, which is the process of controlling the changes to identified items referred to as Configuration Items'

Configuration management is an approach to interoperability testing where tests are executed in the cloud, as the cloud can provide cost-effective access to multiple configurations of the test environments

Configuration management helps ensure that all relevant project documentation and software items are uniquely identified in all their versions and therefore can be unambiguously referenced in test documentation

are often documented following in rule-oriented format using the following template: "As a [role], I want [feature], so that I can [benefit]"

can be written in different formats and represent an aspect of a user story referred to as confirmation' of the so called "3 C's" 

Only developers and testers should be involved in retrospectives, as involving people in other roles is very likely to prevent developers and testers from having open and constructive discussions that really help identify process improvements.

Retrospectives can be very effective in identifying process improvements and can also be very efficient and cost-effective especially since, unlike reviews, they do not require any follow-up activities

On Agile projects, well-conducted retrospectives at the end of each iteration can help the team reduce and sometimes even eliminate the need for dairy stand-up meetings.

During retrospectives, in addition to identifying relevant process improvements, participants should also consider how to implement these improvements and retain them based on the context of the project, such as the software development lifecycle.