Statement coverage measures the percentage of executable statements in the code that have been executed by the tests. It ensures that each line of code is executed at least once, but it has limitations.

Why Option A is Correct:

Missing statements: Statement coverage cannot detect missing statements because it only checks the statements that are present in the code. If a required piece of logic is entirely absent, statement coverage will not identify this issue.

Why Other Options Are Incorrect:

B. Unused branches: While statement coverage does not specifically check branches, it can indirectly highlight branches that are never taken because the corresponding statements within those branches would not be covered.

C. Dead code: Statement coverage will indicate dead code if certain statements are never executed during testing.

D. Unused statement: Statement coverage will show if a statement is never executed, thus identifying unused statements.

Example:

·     Missing Statements: If the code is supposed to handle a specific condition but the corresponding logic is completely missing, statement coverage will not help detect this omission.

·     Unused Branches and Dead Code: If there is a conditional branch or a piece of code that never gets executed, statement coverage will reveal this by showing that certain statements have not been covered.

Statement coverage is useful for identifying unexecuted code but cannot detect missing logic or requirements that have not been implemented in the code.

The partitions are:

(1) below 18

(2) 18-21

(3) more than 21.

So "​22,23,24" falls under the SAME third partition/class.

Boundaries of the partitions are: 9 - 10, 21 - 22.

11 is not a boundary.

The roles and responsibilities of test managers and testers are distinct but complementary. This partition of tasks ensures that testing activities are well-organized and effectively executed.

Why Option B is Correct:

Test Manager:

·     Plans: Develops the test strategy and test plans.

·     Monitors: Keeps track of testing progress and ensures it aligns with the project schedule.

·     Controls: Manages resources, timelines, and ensures adherence to standards and processes.

Tester:

·     Designs: Creates detailed test cases and test scripts based on requirements.

·     Executes: Runs the tests as per the designed test cases.

·     Evaluates: Analyzes test results to identify defects and verify that the system meets the requirements.

Why Other Options Are Incorrect:

A: Suggests the test manager creates test specifications, which is typically the responsibility of the tester. The test manager focuses more on planning and overseeing the testing process.

C: Implies the tester chooses the tools and controls their use, which is usually a collaborative decision involving the test manager to ensure the tools fit the overall strategy and standards.

D: States that the test manager reviews tests and the tester selects tools. While test managers may review tests, their primary role is broader, involving planning and monitoring. Tool selection is typically a joint decision.

Example:

·     Test Manager: Develops a comprehensive test plan outlining the testing approach, resource allocation, and schedule. Monitors testing progress through regular status meetings and adjusts plans as necessary to address any issues.

·     Tester: Creates detailed test cases based on user stories and requirements, executes these tests, and logs defects in the tracking system. Analyzes test results to provide feedback on the system's quality.

This division of tasks ensures a structured and efficient testing process, leveraging the strengths and responsibilities of both roles.

Reliability growth models is a type of Model based testing approach.

Failure to accept allowed credit cards is a product risk. The rest are project risks

A priority rating in a defect report indicates the urgency and importance of fixing the defect. It helps the development team to determine the order in which defects should be addressed.

Why Option A is Correct:

·     Priority Rating: Reflects the urgency of resolving the defect. A high priority defect should be fixed as soon as possible because it might impact critical functionality or have a significant effect on the user experience.

Why Other Options Are Incorrect:

B. To show the highest cost to fix the defect: Priority does not indicate the cost of fixing the defect; it focuses on the urgency and importance.

C. To show which first parts of the system are affected by the defect: Priority does not describe which parts of the system are affected; that information is typically found in the defect description.

D. To show who should fix it first: Priority does not specify the person responsible for fixing the defect; it indicates how urgently the defect needs to be resolved.

Example:

·     High Priority Defect: A critical bug causing the application to crash on startup would have a high priority rating, indicating it needs to be fixed immediately.

·     Low Priority Defect: A minor UI issue that does not affect functionality might have a low priority rating, suggesting it can be addressed later.

By assigning a priority rating, teams can effectively manage their workflow and ensure that the most critical issues are resolved promptly.

Configuration management in testing ensures that test assets are identified, versioned, and traceable to support efficient and accurate testing processes.

Why Option D is Correct:

b. To identify unique items of testware and their related developed software: Configuration management helps in identifying and organizing all the items involved in testing, such as test cases, scripts, and related software.

c. To provide traceability between items of testware and developed software: It ensures that there is a clear relationship between test artifacts and the software components they are testing, which is crucial for impact analysis and change management.

e. To control the versions of software released into the test environment: Configuration management controls and tracks different versions of software to ensure that the correct versions are tested and any changes are properly managed.

Why Other Options Are Incorrect:

a. To choose and implement a suitable configuration management tool: While choosing a tool is part of configuration management, it is not the primary purpose. The main focus is on managing and controlling test artifacts and their versions.

d. To enable users to configure the software: Enabling users to configure the software is not a primary purpose of configuration management in the context of testing. This is more related to deployment or user management.

Example:

·     Identifying Testware: Configuration management ensures that each test case and script is uniquely identified and linked to the specific software version it tests.

·     Traceability: It provides the ability to trace a requirement from development through testing, ensuring that all changes are accounted for and tested appropriately.

·     Version Control: It manages different versions of the software to ensure that testers are working with the correct version, preventing discrepancies and ensuring consistent testing results.

This ensures that testing processes are organized, efficient, and capable of handling changes systematically.

All option are valid test control actions

a, d and f are test planning activities. Designing Test Conditions is done during test analysis. Evaluating test tools is done at any times when needed.