ISTQB Software Testing Quiz 13

1. Which of the following statements about functional testing is true?

Functional testing is primarily concerned with “what” a system does rather than “how” it does it.

Control flow models and menu structure models are used primarily in functional testing.

Functional testing includes, but is not limited to, load testing, stress testing and reliability testing.

Functional testing is often referred to as “structural” testing by testers and developers.

I'm hoping that by now this one would be obvious.

Explanation

I'm hoping that by now this one would be obvious.

2. What is the purpose of exhaustive testing?

To decide if the system is ready for detailed and further testing.

To determine how the existing system may be affected by changes.

To make use of every possible input condition as a test case.

To determine if a system can function correctly with invalid inputs.

The definition of exhaustive testing is that it "comprises all combinations of input values and preconditions", so the anwer is C. But you'll also be aware that according to Testing Principle 2: Exhaustive testing is impossible.

Explanation

The definition of exhaustive testing is that it "comprises all combinations of input values and preconditions", so the anwer is C. But you'll also be aware that according to Testing Principle 2: Exhaustive testing is impossible.

3. What is testing without executing the code?

Non-functional testing

Structure-based testing (white box)

Static testing

Functional testing (black box)

Don't be confused here by structure-based testing, which is clearly done by executing the code (while the test cases can be derived from analysing the code). Static testing, which is the opposite of dynamic testing, is done without executing the code.

Explanation

Don't be confused here by structure-based testing, which is clearly done by executing the code (while the test cases can be derived from analysing the code). Static testing, which is the opposite of dynamic testing, is done without executing the code.

4. Which of the following is a good reason for a developer to use a Test Harness tool?

To help the developer to compare differences between files and databases.

To reduce the quantity of component tests needed to be run.

To make it easier for developers to test each other’s code.

To simplify running unit tests when related components are not available yet.

A test harness consists of drivers and/or stubs. When you want to test a function, but the code to call that function hasn't been written yet, a driver can be used to call the function and allow you to test it. Also, if you want to test a function that needs to call some code, but that code hasn't been written yet, the function can call a stub so you can do your testing.

Explanation

A test harness consists of drivers and/or stubs. When you want to test a function, but the code to call that function hasn't been written yet, a driver can be used to call the function and allow you to test it. Also, if you want to test a function that needs to call some code, but that code hasn't been written yet, the function can call a stub so you can do your testing.

5. Which of the following details would most likely be included in an incident report?

i) Identification of the test item (configuration item) and environment.

ii) Development process characteristics such as organisation stability and test process used.

iii) A review of the test basis, such as requirements, architecture, design, interfaces, etc.

iv) Scope or degree of the impact on the stakeholders’ interests.

I, ii & iii

Ii & iii

I & iv

Iii & iv

This one is easy. Even if you don't know the answer, you can eliminate iii straight away, because incident reports have nothing to do with reviewing anything. So that gets rid of A, B & D and leaves C as the answer.

Explanation

This one is easy. Even if you don't know the answer, you can eliminate iii straight away, because incident reports have nothing to do with reviewing anything. So that gets rid of A, B & D and leaves C as the answer.

6. What factors should an organisation take into account when determining how much testing is needed?

i) Level of risk

ii) Tools to be used during test sub-project

iii) Project constraints such as time and budget

iv) Skill of the testers

v) Expected selling cost of the system

All of the factors should be taken into account.

I & iii

I, iii & iv

I, ii, iv & v

Clearly risk is the main thing to be concerned about, and then we need to factor in time and budget. Tools, skills or selling cost have nothing to do with how much testing is needed (but they may affect how much testing is actually done).

Explanation

Clearly risk is the main thing to be concerned about, and then we need to factor in time and budget. Tools, skills or selling cost have nothing to do with how much testing is needed (but they may affect how much testing is actually done).