a) Ensuring the inclusion of non-functional quality characteristics.

b) Managing test environments subject to continuous changes.

d) Configuring automated tests within the DevOps delivery pipeline.

c) The need to hire additional testers with appropriate experience for manual testing.

b) Defining the requirements for the test environment.

d) Creating a summary test report.

c) Evaluating the testability of the test subject.

a) Analyzing the test basis and test subject.

c) Testers should start designing tests immediately after the draft versions of the relevant work products are made available.

b) The implementation and execution of tests at a given test level should start at the appropriate phase of the development process.

a) Each test level corresponds to specific and distinct test objectives.

d) Every activity related to dynamic testing corresponds to an activity related to static testing.

a) Tracking test progress and identifying areas that require attention.

b) Providing information about the tests performed, their results, and any detected issues and defects.

d) Providing information about tests planned for the next period.

c) Providing information about individual defects, e.g., steps to reproduce them.

c) Validating the fulfillment of legal requirements.

a) Finding defects in the test subject and removing them.

b) Maintaining effective communication with developers.

d) Building trust in the quality of the test subject.

d) Defects may accumulate.

a) Tests wear out.

b) The belief in the absence of defects is a mistake.

c) Early testing saves time and money.

c) 16 hours

a) 14 hours

d) 12 hours

b) 3.5 hours

c) Test quadrants allow stakeholders without technical preparation to more easily understand different types of tests, as well as that some test types at certain levels are more important.

a) Test quadrants facilitate test planning by dividing the testing process into four stages corresponding to the four basic levels of testing: module, integration, system, and acceptance tests.

b) Test quadrants help assess high-level coverage (e.g., requirement coverage) based on low-level coverage (e.g., code coverage).

d) Test quadrants enable agile teams to develop a communication strategy based on classifying people according to the four main psychological types and modeling relationships between these individuals.

c) Feature-driven development.

a) Behavior-driven development.

b) Test-driven development.

d) Performance-driven development.

d) Reducing the level of collaboration with external business users.

c) Faster deployment of products to end users.

a) Improving information exchange between team members.

b) Reducing individual responsibility for quality.