ISTQB Software Testing Quiz 2

1. Repeated testing of an already tested program, after modification, to discover any defects introduced or uncovered as a result of the changes in the software being tested or in another related or unrelated software component is known as:

Re-testing

Confirmation testing

Regression testing

Negative testing

Re-testing and confirmation testing relate to checking that a defect has been fixed. Negative testing is testing with the intention of breaking the system.

Explanation

Re-testing and confirmation testing relate to checking that a defect has been fixed. Negative testing is testing with the intention of breaking the system.

2. One of the fields on a form contains a text box which accepts alphabets in lower or upper case. Identify the invalid Equivalence Class value.

TESTING

TEsting

TEst67g

An Equivalence Class (or Partition) is a portion of the input or output domain for which the behaviour of the system is assumed to be the same, according to the specification. There is no mention of allowing digits in the specification.

Explanation

An Equivalence Class (or Partition) is a portion of the input or output domain for which the behaviour of the system is assumed to be the same, according to the specification. There is no mention of allowing digits in the specification.

3. Deciding how much testing is enough should take into account:
i) Level of risk, including technical and business product and project risk
ii) Project constraints such as time and budget
iii) Size of the testing team
iv) Size of the development team

I, ii, & iii are true; iv is false

I & iv are true; ii & iii are false

I & ii are true; iii & iv are false

Ii, iii & iv are true; i is false

"Size of the development team" is false because this will not necessarily determine how complex the software is and/or how much testing it needs.

"Size of the testing team" is false because this gives no indication of how much testing is needed (it relates only to our capacity to do the testing).

Explanation

"Size of the development team" is false because this will not necessarily determine how complex the software is and/or how much testing it needs.

"Size of the testing team" is false because this gives no indication of how much testing is needed (it relates only to our capacity to do the testing).

4. Defects discovered by static analysis tools include:
i) Variables that are never used
ii) Security vulnerabilities
iii) Programming standard violations
iv) Uncalled functions and procedures

I, ii, iii & iv are true

Iii is true; i, ii & iv are false

I, ii, iii & iv are false

Ii & iv are true; i & iii are false

Static analysis is the analysis of code without executing it. This can also be done on documentation, and can even be carried out by software.

Explanation

Static analysis is the analysis of code without executing it. This can also be done on documentation, and can even be carried out by software.

5. In the following code fragment:
Disc = 0
Order-qty = 0
Read Order-qty
If Order-qty >= 20 then
Disc = 0.05
If Order-qty >= 100 then
Disc = 0.1
End if
End if

What is the minimum number of tests you would need for full statement coverage?

4 tests

1 test

3 tests

2 tests

As long as you had Order-qty being 100 or greater, all the statements would be executed.

IMPORTANT: Don't get "statement coverage" confused with "decision coverage".

Explanation

As long as you had Order-qty being 100 or greater, all the statements would be executed.

IMPORTANT: Don't get "statement coverage" confused with "decision coverage".

6. The structure of an incident report is covered in the Standard for Software and System Test Documentation (IEEE 829), where it is called a(n):

Anomaly report

Defect report

Test defect report

Test incident report

This is just something you have to know, and it's worthwhile flipping through IEEE 829.

Explanation

This is just something you have to know, and it's worthwhile flipping through IEEE 829.