ISTQB Software Testing Quiz 9

1. A test case has which of the following elements?

A test environment description and test instructions.

A set of inputs, execution preconditions, and expected outcomes.

A test plan, test inputs, and logging instructions.

Execution instructions and a function description to determine correct outcome.

This one is just too easy.

Explanation

This one is just too easy.

2. Which of the following are the main stages of a formal review?

Initiation, Preparation, Informal Review Meeting, Status, Rework, and Follow up.

Planning, Preparation, Technical Review, Rework, and Closure.

Preparation, Inspection, Rework, Closure, and Follow up.

Planning, Kick off, Individual Preparation, Review Meeting, Rework, and Follow up.

This is just something you would have to remember.

Explanation

This is just something you would have to remember.

3. In any software development life cycle (SDLC) model, which of the following are characteristics of good testing practices by the test team?

i) Providing complete test coverage of all branches of the system code.

ii) Having a corresponding testing activity for each development activity.

iii) Testers should be involved in reviewing documents as soon as drafts are available.

iv) Each test level has test objectives specific to that level.

Ii, iii & iv

I & iii

I, iii & iv

I & ii

The one that doesn't fit is "providing complete test coverage of all branches of the system code". This type of white box testing is generally impractical (although, for safety-critical systems it might be possible).

Explanation

The one that doesn't fit is "providing complete test coverage of all branches of the system code". This type of white box testing is generally impractical (although, for safety-critical systems it might be possible).

4. Which of the following provides the test group with the ability to reference all documents and software items unambiguously?

Agile testing methodology

Effective use of tools

Configuration management

Requirements traceability matrix

This can be answered by process of elimination. Agile never documents anything. Saying "tools" is meaningless (if we don't specify what type of tool we're talking about). And a requirements matrix has nothing to do with the question.

Explanation

This can be answered by process of elimination. Agile never documents anything. Saying "tools" is meaningless (if we don't specify what type of tool we're talking about). And a requirements matrix has nothing to do with the question.

5. As a test analyst you're collecting measures about defects.

After the first test cycle (covering all requirements) you notice that:

* Subsystem A has a defect density that is 60% lower than the average
* Subsystem B has a defect density that is 150% higher than the average

What conclusions for the next test cycle could you draw from this observation?

Because we have already found many defects in subsystem B, we should concentrate testing resources on Subsystem A.

Observed defect density does not allow any conclusions about the amount of additional testing.

We should try to equalise the amount of testing over all modules to ensure that we test all subsystems evenly.

Defect density is the number of defects divided by the "size" of the component being tested. (The size could be measured in lines of code, number of classes, function points, etc.). According to Testing Principle 4, Defect Clustering, a small number of modules contain most of the defects so a closer examination of subsystem B would be worthwhile.

Explanation

Defect density is the number of defects divided by the "size" of the component being tested. (The size could be measured in lines of code, number of classes, function points, etc.). According to Testing Principle 4, Defect Clustering, a small number of modules contain most of the defects so a closer examination of subsystem B would be worthwhile.

6. Which of the following are success factors when rolling out a new tool?

i) Roll the tool out to the entire organisation to ensure reasonably even coverage.

ii) Avoid changing existing processes to reduce impact of the tool.

iii) Provide training and mentoring to new users.

iv) Allow users to determine where the tool fits into the process best.

I & ii

I, iii & iv

Iii

Iv

I would roll the tool out only to those who need it, or to a pilot group, not to the entire organisation. I would definitely change existing processes, because the tool can often make these more efficient (e.g. Quality Center contains a lot of inbuilt best practice in relation to effective testing processes). And I would not let the users determine where the tool fits in (although I would take their advice on board). When deploying a tool I would create a plan for its deployment, change processes where necessary, listen to the users, and provide training and mentoring to them.

Explanation

I would roll the tool out only to those who need it, or to a pilot group, not to the entire organisation. I would definitely change existing processes, because the tool can often make these more efficient (e.g. Quality Center contains a lot of inbuilt best practice in relation to effective testing processes). And I would not let the users determine where the tool fits in (although I would take their advice on board). When deploying a tool I would create a plan for its deployment, change processes where necessary, listen to the users, and provide training and mentoring to them.