Software Testing Manual Quiz Questions

1.

Deviation from the specific or expected behavior, this is called:

A.

An error
B.

A fault
C.

A failure
D.

A defect
E.

A mistake

Correct Answer
C. A failure

Explanation
A failure refers to a deviation from the specific or expected behavior. It implies that something did not work as intended or desired, resulting in an unsuccessful outcome. This can occur in various contexts, such as technology, systems, processes, or human actions. Unlike errors, faults, defects, or mistakes, a failure specifically emphasizes the lack of success or accomplishment of a particular objective or goal.

Rate this question:

2.

Regression testing should be performed: v) every week w) after the software has changed x) as often as possible y) when the environment has changed z) when the project manager says

A.

V & w are true, x – z are false
B.

W, x & y are true, v & z are false
C.

W & y are true, v, x & z are false
D.

W is true, v, x y and z are false
E.

All of the above are true

Correct Answer
C. W & y are true, v, x & z are false

Explanation
Regression testing should be performed after the software has changed and when the environment has changed. This ensures that any changes made to the software or the environment do not introduce any new defects or issues. Performing regression testing every week or as often as possible may not be necessary and may be time-consuming. The decision to perform regression testing should not be solely based on the project manager's discretion. Therefore, options v, x, and z are false.

Rate this question:

3.

IEEE 829 test plan documentation standard contains all of the following except:

A.

Test items
B.

Test deliverables
C.

Test tasks
D.

Test environment
E.

Test specification

Correct Answer
E. Test specification

Explanation
The IEEE 829 test plan documentation standard includes test items, test deliverables, test tasks, and test environment. However, it does not include test specification. Test specification refers to the detailed description of the test cases, test data, and expected results for a specific test. While test specification is an important component of test planning, it is not specifically mentioned in the IEEE 829 standard.

Rate this question:

4.

Testing should be stopped when:

A.

All the planned tests have been run
B.

Time has run out
C.

All faults have been fixed correctly
D.

both a) and c)
E.

It depends on the risks for the system being tested

Correct Answer
E. It depends on the risks for the system being tested

Explanation
Testing should be stopped when it depends on the risks for the system being tested. This means that the decision to stop testing should be based on the level of risk associated with the system. If the risks are deemed acceptable and all planned tests have been run and faults have been fixed correctly, then testing can be stopped. However, if there are still significant risks associated with the system, testing should continue until those risks are mitigated. The time factor is not the sole determinant for stopping testing, but rather the level of risk involved.

Rate this question:

5.

Order numbers on a stock control system can range between 10000 and 99999 inclusive. Which of the following inputs might be a result of designing tests for only valid equivalence classes and valid boundaries:

A.

1000, 5000, 99999
B.

9999, 50000, 100000
C.

10000, 50000, 99999
D.

10000, 99999
E.

9999, 10000, 50000, 99999, 10000

Correct Answer
C. 10000, 50000, 99999

Explanation
The given inputs 10000, 50000, and 99999 are valid equivalence classes and valid boundaries for the order numbers on the stock control system. 10000 represents the minimum valid value, 50000 represents a value within the valid range, and 99999 represents the maximum valid value. Testing with these inputs ensures that the system can handle the lower boundary, values within the valid range, and the upper boundary effectively.

Rate this question:

6.

Consider the following statements about early test design: i. early test design can prevent fault multiplication ii. faults found during early test design are more expensive to fix iii. early test design can find faults iv. early test design can cause changes to the requirements v. early test design takes more effort

A.

I, iii & iv are true. Ii & v are false
B.

iii is true, I, ii, iv & v are false
C.

Iii & iv are true. i, ii & v are false
D.

I, iii, iv & v are true, ii us false
E.

I & iii are true, ii, iv & v are false

Correct Answer
A. I, iii & iv are true. Ii & v are false

Explanation
Early test design refers to the practice of designing tests at the early stages of the software development life cycle. Statement i states that early test design can prevent fault multiplication, which means that by identifying and fixing faults early on, the likelihood of those faults propagating and causing further issues is reduced. Statement iii states that early test design can find faults, indicating that designing tests early can help uncover defects in the system. Statement iv suggests that early test design can cause changes to the requirements, implying that the process of designing tests may reveal flaws or inconsistencies in the requirements, leading to necessary changes. On the other hand, statement ii states that faults found during early test design are more expensive to fix, which contradicts the idea that early detection and correction of faults can save costs. Statement v claims that early test design takes more effort, which contradicts the notion that designing tests early can be more efficient.

Rate this question:

7.

Non-functional system testing includes:

A.

Testing to see where the system does not function properly
B.

Testing quality attributes of the system including performance and usability
C.

Testing a system feature using only the software required for that action
D.

Testing a system feature using only the software required for that function
E.

Testing for functions that should not exist

Correct Answer
B. Testing quality attributes of the system including performance and usability

Explanation
Non-functional system testing focuses on evaluating the quality attributes of the system, such as its performance and usability. This type of testing aims to ensure that the system meets the required standards in terms of its non-functional aspects, rather than solely testing its functional capabilities. By conducting non-functional system testing, organizations can identify any performance or usability issues and make necessary improvements to enhance the overall quality of the system.

Rate this question:

8.

Which of the following is NOT part of configuration management:

A.

Status accounting of configuration items
B.

auditing conformance to ISO9001
C.

identification of test versions
D.

Record of changes to documentation over time
E.

Controlled library access

Correct Answer
B. auditing conformance to ISO9001

Explanation
Auditing conformance to ISO9001 is not part of configuration management because it is a quality management standard that focuses on ensuring consistent quality in products and services. Configuration management, on the other hand, is a process that involves managing and controlling changes to the configuration of a system or product throughout its lifecycle. While auditing may be a part of quality management, it is not specifically related to configuration management.

Rate this question:

9.

Which of the following is the main purpose of the integration strategy for integration testing in the small?

A.

To ensure that all of the small modules are tested adequately
B.

To ensure that the system interfaces to other systems and networks
C.

To specify which modules to combine when and how many at once
D.

To ensure that the integration testing can be performed by a small team
E.

To specify how the software should be divided into modules

Correct Answer
C. To specify which modules to combine when and how many at once

Explanation
The main purpose of the integration strategy for integration testing in the small is to specify which modules to combine when and how many at once. This means that the strategy outlines the specific modules that need to be integrated, the order in which they should be combined, and the number of modules that should be integrated at a given time. This ensures a systematic and controlled approach to integration testing, allowing for better management of dependencies and potential issues that may arise during the integration process.

Rate this question:

10.

What is the purpose of test completion criteria in a test plan:

A.

To know when a specific test has finished its execution
B.

To ensure that the test case specification is complete
C.

To set the criteria used in generating test inputs
D.

To know when test planning is complete
E.

To plan when to stop testing

Correct Answer
E. To plan when to stop testing

Explanation
The purpose of test completion criteria in a test plan is to plan when to stop testing. This criteria helps in determining the point at which the testing process can be considered complete and the product can be released. It sets specific conditions or milestones that need to be met in order to decide that sufficient testing has been conducted. This ensures that testing is not prolonged unnecessarily and helps in managing the overall testing effort effectively.

Rate this question: