Condition testing

Statement testing

Path testing

Equivalence partitioning

c) PT3

d) PT4

b) PT2

a) PT1

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

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

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

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

d) Creating a summary test report.

b) Defining the requirements for the test environment.

c) Evaluating the testability of the test subject.

a) Analyzing the test basis and test subject.

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

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

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.

c) Validating the fulfillment of legal requirements.

b) Maintaining effective communication with developers.

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

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

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

d) Configuring automated tests within the DevOps delivery pipeline.

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

b) Managing test environments subject to continuous changes.

a) Behavior-driven development.

b) Test-driven development.

d) Performance-driven development.

c) Feature-driven development.

d) Retrospectives serve as a forum for agile team members to discuss the plan and technical decisions for the next iteration.

b) Retrospectives give testers the opportunity to identify actions that were successful and should be retained after implementing any improvements in the future.

a) Retrospectives allow team members to point out individuals who participated too little in improving quality, as required by the "whole team" approach.

c) Retrospectives are an opportunity for agile team members to provide critical feedback to management and clients without fear of taking responsibility.

a) Adding information about which users and which books are affected by the issue to the "Description" section.

d) Repeating the same test case in different environments and creating a separate defect report for each of them.

b) Providing the missing value in the "Priority" field.

c) Adding screenshots and database state images after each step described in the "Steps to reproduce the defect" section to the "Attachments" section.