[ISTQB Mexico Study Group 2] Chaps 1 To 4

Test Implementation and execution

Test Analysis and Design

Evaluating the Exit Criteria and reporting

Test Closure Activities

I,ii,iii are true and iv is false

I,,iv are true and ii is false

I,ii are true and iii,iv are false

Ii,iii,iv are true and i is false

I,ii,iii are true and iv is false

I,iii,iv are true and ii is false

Ii,iii are true and i and iv are false

I,ii are false and iii , iv are true

Static testing requires the running of tests through the code

Static testing includes desk checking

Static testing includes techniques such as reviews and inspections

Static testing can give measurements such as cyclomatic complexity

I,ii,iii,iv are true

I is true and ii,iii,iv are false

I,ii,iii are true and iv is false

Ii is true and i,iii,iv are false

I,ii,iii are true and iv is false

I,ii,iii,iv are false

I,ii,iv are true and iii is false

All of above are true

Defect clustering

Early testing

Pesticide paradox

Testing shows presence of defects

Ii is true and i,iii,iv are false

I,iii,iv are true and ii is false

I,iii,iv are false and ii is true

Iii is true and i,ii,iv are false

I,ii,iii,iv,v,vi

Vi,i,ii,iii,iv,v

I,v,iv,ii,iii,vi

I,ii,iii,v,iv,vi

Structural Testing

Design Based Testing

Error Guessing Technique

Experience Based Technique

Is impractical but possible

Is practically possible

Is impractical and impossible

Is always possible

Creating test suites from the test cases

Executing test cases either manually or by using test execution tools

Comparing actual results

Designing the Tests

Decision D has not been tested completely.

100% decision coverage has been achieved.

100% decision coverage has been achieved.

Decision F not been tested completely

Decision table testing

State transition testing

Use case testing

Equivalence partitioning

Static analysis supported by tools may find defects prior to manual test execution.

Static analysis supported by tools prevents business analysts and requirement engineers building software models (e.g. state transition diagrams), which do not match the requirements.

By using static analysis tools user acceptance testing can be shortened because the users need to execute less tests

By performing static analysis of the code supported by tools the need for the developers doing unit testing is decreased.

Exhaustive testing is impossible

Defect clustering

Pesticide paradox

Absence-of-errors fallacy

Test principles only affect the preparation for testing

Test principles only affect test execution activities

Test principles affect the early test activities such as review

Test principles affect activities throughout the test life cycle

Includes Metrics

Pre Meeting Preparations

Scenario , Dry Run , Peer Group

Formal Follow Up Process

The use of a variable before it has been defined

Unreachable (“dead”) code

Memory leaks

Array bound violations

V, W, Y and Z

U, V, W and Y

U, X and Y

V, W and Y

User requirements

Risk analysis reports

Component requirements

Use cases

Objectives are the same for each test level

The objectives of a test level don't need t be defined in advance

Each level has objectives specific to that level

Objectives should be generic for any test level

Performed by customers at their own site

Performed by customers at the software developer's site

Performed by an independent test team

Useful to test software developed for a specific customer or user

They depend on the tester's understanding of the way the system is structured rather than on a documented record of what the system should do.

They depend on having older testers rather than younger testers.

They depend on a documented record of what the system should do rather than on an individual's personal view.

They depend on an individual's personal view rather than on a documented record of what the system should do.

X, Y and Z

V, X, Y and Z

W,X and Y

V, X and Z