Software Testing Practice Test

Question 1

Software testing should begin

Accepted Answer

as soon as possible in the development life cycle

Answer

Modern software development emphasizes 'shift-left' testing, meaning testing activities should commence as early as possible in the development life cycle. This includes reviewing requirements, designing test cases during the design phase, and performing static analysis on code. Early testing helps identify defects when they are cheaper and easier to fix, reducing overall project costs and improving software quality.

Question 2

Which of the following is not a component of the Test Execution and Implementation Phase?

Accepted Answer

Designing the Tests

Answer

The Test Execution and Implementation Phase focuses on running the tests and managing the results. This includes creating test suites, executing test cases, and comparing actual results to expected outcomes. 'Designing the Tests' is a distinct activity that occurs earlier, typically in the Test Analysis and Design phase, where test conditions and test cases are conceptualized and specified.

Question 3

Which of the following is NOT typically included in a test plan?

Accepted Answer

Incident reports

Answer

A test plan outlines the scope, objectives, resources, and schedule of testing activities. It typically includes features to be tested, risks, and the testing schedule. Incident reports, which document defects found during testing, are outputs of the test execution phase and are usually managed separately, though their reporting process might be defined within the test plan.

Question 4

All of the following can be found during inspections, with the exception of

Accepted Answer

How much of the code has been covered

Answer

Inspections are a static testing technique where code or documents are manually reviewed to find defects, such as undefined variables, missing requirements, or grammatical errors. However, 'how much of the code has been covered' (code coverage) is a dynamic testing metric, measured by executing the code with test cases, not by static inspection.

Question 5

Equivalence partitioning is defined as

Accepted Answer

black box testing technique appropriate to all levels of testing

Answer

Equivalence partitioning is a black-box testing technique where input data is divided into partitions (or classes) of equivalent data. The assumption is that if one condition in a partition works, all will work, and if one fails, all will fail. This technique is highly effective for reducing the number of test cases while maintaining test coverage and can be applied at all levels of testing.