Testing Manual Quiz

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 indicates that something did not work as intended or did not meet the desired outcome. It can be seen as a result of an error, fault, defect, or mistake, but specifically refers to the overall outcome not being achieved.

Rate this question:

1
0
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 is because regression testing is conducted to ensure that the changes made to the software do not introduce new bugs or issues, and that the software still functions correctly in the updated environment. Performing regression testing every week or as often as possible may not be necessary or practical, and it should not be solely dependent on the project manager's decision. 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 tests to be performed, including the input data, expected output, and any specific conditions or requirements. While test specification is an important component of a test plan, it is not specifically mentioned in the IEEE 829 standard.

Rate this question:

0
1
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 testing should continue until the risks associated with the system have been adequately addressed. It is important to consider the potential impact and severity of any remaining risks before deciding to stop testing. Simply running all planned tests or fixing all faults may not be sufficient if there are still significant risks present in the system. Time constraints can also be a factor, but ultimately the decision to stop testing should be based on the level of risk that remains.

Rate this question:

2
1
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 because they represent the minimum, middle, and maximum values within the range of 10000 to 99999. By testing these inputs, we can ensure that the stock control system correctly handles the lower boundary, an average value, and the upper boundary of the valid range.

Rate this question:

2
1
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 can prevent fault multiplication by identifying and addressing potential faults early in the development process. It can also find faults that may have been missed during other stages of testing. Additionally, early test design can cause changes to the requirements as faults are identified and addressed. However, it is not necessarily more expensive to fix faults found during early test design, and it may not always require more effort compared to other testing stages.

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 refers to the testing of quality attributes of the system, such as performance and usability. This type of testing focuses on evaluating how well the system performs under different conditions and how user-friendly it is. It helps to identify any issues or deficiencies in these non-functional aspects of the system, allowing for improvements to be made before the system is deployed to users.

Rate this question:

1
0
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 ISO9001 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 identifying, organizing, and controlling the configuration items of a system throughout its lifecycle. It includes activities such as status accounting, identification of test versions, record of changes to documentation, and controlled library access. Auditing conformance to ISO9001 is a separate process that ensures compliance with the quality management standard, but it is not directly 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 combined at a time. This helps ensure a systematic and controlled approach to integration testing, allowing for efficient and effective testing of the software.

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 when the testing activities have been completed and the desired level of test coverage has been achieved. It sets specific conditions or milestones that need to be met in order to consider the testing phase complete. This ensures that testing is not prolonged indefinitely and helps in making informed decisions regarding the release of the software.

Rate this question:

1
0

Testing Manual Quiz

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

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

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

Testing should be stopped when:

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:

Non-functional system testing includes:

Which of the following is NOT part of configuration management:

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

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