67
Principles of Testing 1 Principles 2 Lifecycle 4 Dynamic test techniques 3 Static testing 5 Management 6 Tools Software Testing ISTQB / ISEB Foundation Exam Practice Chapter 1

ISTQB / ISEB Foundation Exam Practice -1

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: ISTQB / ISEB Foundation Exam Practice -1

Principles of Testing

1 Principles 2 Lifecycle

4 Dynamic testtechniques

3 Static testing

5 Management 6 Tools

Software Testing

ISTQB / ISEB Foundation Exam Practice

Chapter 1

Page 2: ISTQB / ISEB Foundation Exam Practice -1

Contents

Why testing is necessary

Fundamental test process

Psychology of testing

Re-testing and regression testing

Expected results

Prioritisation of tests

Principles

1 2 3

4 5 6

ISTQB / ISEB Foundation Exam Practice

Page 3: ISTQB / ISEB Foundation Exam Practice -1

Testing terminology

No generally accepted set of testing definitions used world wide

New standard BS 7925-1- Glossary of testing terms (emphasis on component Glossary of testing terms (emphasis on component

testing)testing)- most recentmost recent- developed by a working party of the BCS SIGISTdeveloped by a working party of the BCS SIGIST- adopted by the ISEB / ISTQBadopted by the ISEB / ISTQB

Page 4: ISTQB / ISEB Foundation Exam Practice -1

What is a “bug”?

Error: a human action that produces an incorrect result

Fault: a manifestation of an error in software- also known as a defect or bug also known as a defect or bug - if executed, a fault may cause a failureif executed, a fault may cause a failure

Failure: deviation of the software from its expected delivery or service - (found defect)(found defect)

Failure is an event; fault is a state of

the software, caused by an error

Failure is an event; fault is a state of

the software, caused by an error

Page 5: ISTQB / ISEB Foundation Exam Practice -1

Error - Fault - Failure

A person makesan error ...

… that creates afault in thesoftware ...

… that can causea failure

in operation

Page 6: ISTQB / ISEB Foundation Exam Practice -1

Reliability versus faults

Reliability: the probability that software will not cause the failure of the system for a specified time under specified conditions- Can a system be fault-free? (zero faults, right first Can a system be fault-free? (zero faults, right first

time)time)- Can a software system be reliable but still have Can a software system be reliable but still have

faults?faults?- Is a “fault-free” software application always Is a “fault-free” software application always

reliable?reliable?

Page 7: ISTQB / ISEB Foundation Exam Practice -1

Why do faults occur in software?

software is written by human beings- who know something, but not everythingwho know something, but not everything- who have skills, but aren’t perfectwho have skills, but aren’t perfect- who do make mistakes (errors)who do make mistakes (errors)

under increasing pressure to deliver to strict deadlines- no time to check but assumptions may be wrongno time to check but assumptions may be wrong- systems may be incompletesystems may be incomplete

if you have ever written software ...

Page 8: ISTQB / ISEB Foundation Exam Practice -1

What do software faults cost?

huge sums- Ariane 5 ($7billion)Ariane 5 ($7billion)- Mariner space probe to Venus ($250m)Mariner space probe to Venus ($250m)- American Airlines ($50m)American Airlines ($50m)

very little or nothing at all- minor inconvenienceminor inconvenience- no visible or physical detrimental impactno visible or physical detrimental impact

software is not “linear”: - small input may have very large effectsmall input may have very large effect

Page 9: ISTQB / ISEB Foundation Exam Practice -1

Safety-critical systems

software faults can cause death or injury- radiation treatment kills patients (Therac-25)radiation treatment kills patients (Therac-25)- train driver killedtrain driver killed- aircraft crashes (Airbus & Korean Airlines)aircraft crashes (Airbus & Korean Airlines)- bank system overdraft letters cause suicidebank system overdraft letters cause suicide

Page 10: ISTQB / ISEB Foundation Exam Practice -1

So why is testing necessary?

- because software is likely to have faultsbecause software is likely to have faults- to learn about the reliability of the softwareto learn about the reliability of the software- to fill the time between delivery of the software and to fill the time between delivery of the software and

the release datethe release date- to prove that the software has no faultsto prove that the software has no faults- because testing is included in the project planbecause testing is included in the project plan- because failures can be very expensivebecause failures can be very expensive- to avoid being sued by customersto avoid being sued by customers- to stay in businessto stay in business

Page 11: ISTQB / ISEB Foundation Exam Practice -1

Why not just "test everything"?

system has20 screens

Average: 10 fields / screen2 types input / field(date as Jan 3 or 3/1)(number as integer or decimal)Around 100 possible values

Total for 'exhaustive' testing:

20 x 4 x 3 x 10 x 2 x 100 = 20 x 4 x 3 x 10 x 2 x 100 = 480,000 tests480,000 tests

If 1 second per test, 8000 mins, 133 hrs, 17.7 days

(not counting finger trouble, faults or retest)

Avr. 4 menus3 options / menu

10 secs = 34 wks, 1 min = 4 yrs, 10 min = 40 yrs

Page 12: ISTQB / ISEB Foundation Exam Practice -1

Exhaustive testing?

What is exhaustive testing?- when all the testers are exhaustedwhen all the testers are exhausted- when all the planned tests have been executedwhen all the planned tests have been executed- exercising all combinations of inputs and exercising all combinations of inputs and

preconditionspreconditions How much time will exhaustive testing take?

- infinite timeinfinite time- not much timenot much time- impractical amount of timeimpractical amount of time

Page 13: ISTQB / ISEB Foundation Exam Practice -1

How much testing is enough?

- it’s never enoughit’s never enough- when you have done what you plannedwhen you have done what you planned- when your customer/user is happywhen your customer/user is happy- when you have proved that the system works when you have proved that the system works

correctlycorrectly- when you are confident that the system works when you are confident that the system works

correctlycorrectly- it depends on the risks for your systemit depends on the risks for your system

Page 14: ISTQB / ISEB Foundation Exam Practice -1

How much testing?

It depends on RISKRISK- riskrisk of missing important faults of missing important faults- riskrisk of incurring failure costs of incurring failure costs- riskrisk of releasing untested or under-tested software of releasing untested or under-tested software- riskrisk of losing credibility and market share of losing credibility and market share- riskrisk of missing a market window of missing a market window- riskrisk of over-testing, ineffective testing of over-testing, ineffective testing

Page 15: ISTQB / ISEB Foundation Exam Practice -1

- what not to test (this time)what not to test (this time)

use RISKRISK to

- allocate the time available for testing by allocate the time available for testing by prioritising testing ...prioritising testing ...

So little time, so much to test ..

test time will always be limited

use RISKRISK to determine:

- what to test firstwhat to test first- what to test mostwhat to test most- how thoroughly to test each itemhow thoroughly to test each item } i.e. where to

place emphasis

Page 16: ISTQB / ISEB Foundation Exam Practice -1

Most important principle

Prioritise tests

so that,

whenever you stop testing,

you have done the best testing

in the time available.

Prioritise tests

so that,

whenever you stop testing,

you have done the best testing

in the time available.

Page 17: ISTQB / ISEB Foundation Exam Practice -1

Testing and quality

testing measures software quality testing can find faults; when they are

removed, software quality (and possibly reliability) is improved

what does testing test?- system function, correctness of operationsystem function, correctness of operation- non-functional qualities: reliability, usability, non-functional qualities: reliability, usability,

maintainability, reusability, testability, etc.maintainability, reusability, testability, etc.

Page 18: ISTQB / ISEB Foundation Exam Practice -1

Other factors that influence testing

contractual requirements legal requirements industry-specific requirements

- e.g. pharmaceutical industry (FDA), compiler e.g. pharmaceutical industry (FDA), compiler standard tests, safety-critical or safety-related such standard tests, safety-critical or safety-related such as railroad switching, air traffic controlas railroad switching, air traffic control

It is difficult to determine

how much testing is enough

but it is not impossible

It is difficult to determine

how much testing is enough

but it is not impossible

Page 19: ISTQB / ISEB Foundation Exam Practice -1

Contents

Why testing is necessary

Fundamental test process

Psychology of testing

Re-testing and regression testing

Expected results

Prioritisation of tests

Principles

1 2 3

4 5 6

ISTQB / ISEB Foundation Exam Practice

Page 20: ISTQB / ISEB Foundation Exam Practice -1

Test Planning - different levels

TestPolicy

TestStrategy

Company level

High LevelTest Plan

High LevelTest Plan

Project level (IEEE 829)(one for each project)

DetailedTest Plan

DetailedTest Plan

DetailedTest Plan

DetailedTest Plan

Test stage level (IEEE 829)(one for each stage within a project,e.g. Component, System, etc.)

Page 21: ISTQB / ISEB Foundation Exam Practice -1

The test process

specification execution recordingcheck

completion

Planning (detailed level)

Page 22: ISTQB / ISEB Foundation Exam Practice -1

Test planning

how the test strategy and project test plan apply to the software under test

document any exceptions to the test strategy- e.g. only one test case design technique needed for e.g. only one test case design technique needed for

this functional area because it is less criticalthis functional area because it is less critical other software needed for the tests, such as

stubs and drivers, and environment details set test completion criteria

Page 23: ISTQB / ISEB Foundation Exam Practice -1

Test specification

specification execution recordingcheck

completion

Identify conditions

Design test cases

Build tests

Planning (detailed level)

Page 24: ISTQB / ISEB Foundation Exam Practice -1

A good test case

effective

exemplary

evolvable

economic

Finds faults

Represents others

Easy to maintain

Cheap to use

Page 25: ISTQB / ISEB Foundation Exam Practice -1

Test specification

test specification can be broken down into three distinct tasks:

1.1. identify: identify: determine ‘what’ is to be tested (identifydetermine ‘what’ is to be tested (identifytest conditions) and prioritisetest conditions) and prioritise

2.2. design: design: determine ‘how’ the ‘what’ is to be testeddetermine ‘how’ the ‘what’ is to be tested(i.e. design test cases)(i.e. design test cases)

3.3. build: build: implement the tests (data, scripts, etc.)implement the tests (data, scripts, etc.)

Page 26: ISTQB / ISEB Foundation Exam Practice -1

Task 1: identify conditions

list the conditions that we would like to test:- use the test design techniques specified in the test planuse the test design techniques specified in the test plan- there may be many conditions for each system function or there may be many conditions for each system function or

attributeattribute- e.g.e.g.

• ““life assurance for a winter sportsman”life assurance for a winter sportsman”

• ““number items ordered > 99”number items ordered > 99”

• ““date = 29-Feb-2004”date = 29-Feb-2004” prioritise the test conditions

- must ensure most important conditions are coveredmust ensure most important conditions are covered

(determine ‘what’ is to be tested and prioritise)

Page 27: ISTQB / ISEB Foundation Exam Practice -1

Selecting test conditions

Importance

Time

Best setFirst set

Page 28: ISTQB / ISEB Foundation Exam Practice -1

Task 2: design test cases

design test input and test data- each test exercises one or more test conditionseach test exercises one or more test conditions

determine expected results- predict the outcome of each test case, what is predict the outcome of each test case, what is

output, what is changed and what is not changedoutput, what is changed and what is not changed design sets of tests

- different test sets for different objectives such as different test sets for different objectives such as regression, building confidence, and finding faultsregression, building confidence, and finding faults

(determine ‘how’ the ‘what’ is to be tested)

Page 29: ISTQB / ISEB Foundation Exam Practice -1

Designing test cases

Importance

Time

Most importanttest conditions

Least importanttest conditions

Test cases

Page 30: ISTQB / ISEB Foundation Exam Practice -1

Task 3: build test cases

prepare test scripts- less system knowledge tester has the more detailed less system knowledge tester has the more detailed

the scripts will have to bethe scripts will have to be- scripts for tools have to specify every detailscripts for tools have to specify every detail

prepare test data- data that must exist in files and databases at the start data that must exist in files and databases at the start

of the testsof the tests prepare expected results

- should be defined before the test is executedshould be defined before the test is executed

(implement the test cases)

Page 31: ISTQB / ISEB Foundation Exam Practice -1

Test execution

specification execution recordingcheck

completion

Planning (detailed level)

Page 32: ISTQB / ISEB Foundation Exam Practice -1

Execution

Execute prescribed test cases- most important ones firstmost important ones first- would not execute all test cases ifwould not execute all test cases if

• testing only fault fixestesting only fault fixes

• too many faults found by early test casestoo many faults found by early test cases

• time pressure time pressure

- can be performed manually or automatedcan be performed manually or automated

Page 33: ISTQB / ISEB Foundation Exam Practice -1

Test recording

specification execution recordingcheck

completion

Planning (detailed level)

Page 34: ISTQB / ISEB Foundation Exam Practice -1

Test recording 1

The test record contains:- identities and versions (unambiguously) ofidentities and versions (unambiguously) of

• software under testsoftware under test

• test specificationstest specifications Follow the plan

- mark off progress on test scriptmark off progress on test script

- document actual outcomes from the testdocument actual outcomes from the test

- capture any other ideas you have for new test casescapture any other ideas you have for new test cases

- note that these records are used to establish that all test note that these records are used to establish that all test activities have been carried out as specifiedactivities have been carried out as specified

Page 35: ISTQB / ISEB Foundation Exam Practice -1

Test recording 2

Compare actual outcome with expected outcome. Log discrepancies accordingly:- software faultsoftware fault- test fault (e.g. expected results wrong)test fault (e.g. expected results wrong)- environment or version faultenvironment or version fault- test run incorrectlytest run incorrectly

Log coverage levels achieved (for measures specified as test completion criteria)

After the fault has been fixed, repeat the required test activities (execute, design, plan)

Page 36: ISTQB / ISEB Foundation Exam Practice -1

Check test completion

specification execution recordingcheck

completion

Planning (detailed level)

Page 37: ISTQB / ISEB Foundation Exam Practice -1

Check test completion

Test completion criteria were specified in the test plan

If not met, need to repeat test activities, e.g. test specification to design more tests

specification execution recordingcheck

completion

Coverage too low

CoverageOK

Page 38: ISTQB / ISEB Foundation Exam Practice -1

Test completion criteria

Completion or exit criteria apply to all levels of testing - to determine when to stop- coverage, using a measurement technique, e.g.coverage, using a measurement technique, e.g.

• branch coverage for unit testingbranch coverage for unit testing

• user requirementsuser requirements

• most frequently used transactionsmost frequently used transactions

- faults found (e.g. versus expected)faults found (e.g. versus expected)- cost or timecost or time

Page 39: ISTQB / ISEB Foundation Exam Practice -1

Comparison of tasks

Clerical

Intellectual

one-offactivity

activityrepeated

many times

Governs thequality of tests

Good toautomate

Execute

Recording

Planning

Specification

Page 40: ISTQB / ISEB Foundation Exam Practice -1

Contents

Why testing is necessary

Fundamental test process

Psychology of testing

Re-testing and regression testing

Expected results

Prioritisation of tests

Principles

1 2 3

4 5 6

ISTQB / ISEB Foundation Exam Practice

Page 41: ISTQB / ISEB Foundation Exam Practice -1

Why test?

build confidence prove that the software is correct demonstrate conformance to requirements find faults reduce costs show system meets user needs assess the software quality

Page 42: ISTQB / ISEB Foundation Exam Practice -1

Fault foundFaults found

Confidence

Time

Confidence

No faults found = confidence?

Page 43: ISTQB / ISEB Foundation Exam Practice -1

FewFaults

ManyFaults

FewFaults

FewFaults

FewFaults

You may be here

You thinkyou are here

TestQuality

Low

High

Software QualityLow High

Assessing software quality

Page 44: ISTQB / ISEB Foundation Exam Practice -1

A traditional testing approach

Show that the system:- does what it shoulddoes what it should- doesn't do what it shouldn'tdoesn't do what it shouldn't

Fastest achievement: easy test cases

Goal: show working

Success: system works

Goal: show working

Success: system works

Result: faults left inResult: faults left in

Page 45: ISTQB / ISEB Foundation Exam Practice -1

A better testing approach

Show that the system:- does what it shouldn'tdoes what it shouldn't- doesn't do what it shoulddoesn't do what it should

Fastest achievement: difficult test cases

Goal: find faults

Success: system fails

Goal: find faults

Success: system fails

Result: fewer faults left inResult: fewer faults left in

Page 46: ISTQB / ISEB Foundation Exam Practice -1

The testing paradox

Purpose of testing: to find faults

The best way to build confidence

is to try to destroy it

The best way to build confidence

is to try to destroy it

Purpose of testing: build confidence

Finding faults destroys confidence

Purpose of testing: destroy confidence

Page 47: ISTQB / ISEB Foundation Exam Practice -1

Who wants to be a tester?

A destructive process Bring bad news (“your baby is ugly”) Under worst time pressure (at the end) Need to take a different view, a different

mindset (“What if it isn’t?”, “What could go wrong?”)

How should fault information be communicated (to authors and managers?)

Page 48: ISTQB / ISEB Foundation Exam Practice -1

Tester’s have the right to:

- accurate information about progress and changesaccurate information about progress and changes- insight from developers about areas of the softwareinsight from developers about areas of the software- delivered code tested to an agreed standarddelivered code tested to an agreed standard- be regarded as a professional (no abuse!)be regarded as a professional (no abuse!)- find faults!find faults!- challenge specifications and test planschallenge specifications and test plans- have reported faults taken seriously (non-reproducible)have reported faults taken seriously (non-reproducible)- make predictions about future fault levelsmake predictions about future fault levels- improve your own testing processimprove your own testing process

Page 49: ISTQB / ISEB Foundation Exam Practice -1

Testers have responsibility to:

- follow the test plans, scripts etc. as documented follow the test plans, scripts etc. as documented - report faults objectively and factually (no abuse!)report faults objectively and factually (no abuse!)- check tests are correct before reporting s/w faultscheck tests are correct before reporting s/w faults- remember it is the software, not the programmer, remember it is the software, not the programmer,

that you are testingthat you are testing- assess risk objectivelyassess risk objectively- prioritise what you report prioritise what you report - communicate the truthcommunicate the truth

Page 50: ISTQB / ISEB Foundation Exam Practice -1

Independence

Test your own work?- find 30% - 50% of your own faultsfind 30% - 50% of your own faults- same assumptions and thought processessame assumptions and thought processes- see what you meant or want to see, not what is theresee what you meant or want to see, not what is there- emotional attachment emotional attachment

• don’t want to find faultsdon’t want to find faults

• actively want NOT to find faultsactively want NOT to find faults

Page 51: ISTQB / ISEB Foundation Exam Practice -1

Levels of independence

None: tests designed by the person who wrote the software

Tests designed by a different person Tests designed by someone from a different

department or team (e.g. test team) Tests designed by someone from a different

organisation (e.g. agency) Tests generated by a tool (low quality tests?)

Page 52: ISTQB / ISEB Foundation Exam Practice -1

Contents

Why testing is necessary

Fundamental test process

Psychology of testing

Re-testing and regression testing

Expected results

Prioritisation of tests

Principles

1 2 3

4 5 6

ISTQB / ISEB Foundation Exam Practice

Page 53: ISTQB / ISEB Foundation Exam Practice -1

Re-testing after faults are fixed

Run a test, it fails, fault reported New version of software with fault “fixed” Re-run the same test (i.e. re-test)

- must be exactly repeatablemust be exactly repeatable- same environment, versions (except for the software same environment, versions (except for the software

which has been intentionally changed!)which has been intentionally changed!)- same inputs and preconditionssame inputs and preconditions

If test now passes, fault has been fixed correctly - or has it?

Page 54: ISTQB / ISEB Foundation Exam Practice -1

Re-testing (re-running failed tests)

x

x

x

x

New faults introduced by the firstfault fix not found during re-testing

Re-test to checkFault now fixed

Page 55: ISTQB / ISEB Foundation Exam Practice -1

Regression test

to look for any unexpected side-effects

x

x

x

xCan’t guaranteeto find them all

Page 56: ISTQB / ISEB Foundation Exam Practice -1

Regression testing 1

misnomer: "anti-regression" or "progression" standard set of tests - regression test pack at any level (unit, integration, system,

acceptance) well worth automating a developing asset but needs to be maintained

Page 57: ISTQB / ISEB Foundation Exam Practice -1

Regression testing 2

Regression tests are performed- after software changes, including faults fixedafter software changes, including faults fixed- when the environment changes, even if application when the environment changes, even if application

functionality stays the samefunctionality stays the same- for emergency fixes (possibly a subset)for emergency fixes (possibly a subset)

Regression test suites- evolve over timeevolve over time- are run oftenare run often- may become rather largemay become rather large

Page 58: ISTQB / ISEB Foundation Exam Practice -1

Regression testing 3

Maintenance of the regression test pack- eliminate repetitive tests (tests which test the same eliminate repetitive tests (tests which test the same

test condition)test condition)- combine test cases (e.g. if they are always run combine test cases (e.g. if they are always run

together)together)- select a different subset of the full regression suite select a different subset of the full regression suite

to run each time a regression test is neededto run each time a regression test is needed- eliminate tests which have not found a fault for a eliminate tests which have not found a fault for a

long time (e.g. old fault fix tests)long time (e.g. old fault fix tests)

Page 59: ISTQB / ISEB Foundation Exam Practice -1

Regression testing and automation

Test execution tools (e.g. capture replay) are regression testing tools - they re-execute tests which have already been executed

Once automated, regression tests can be run as often as desired (e.g. every night)

Automating tests is not trivial (generally takes 2 to 10 times longer to automate a test than to run it manually

Don’t automate everything - plan what to automate first, only automate if worthwhile

Page 60: ISTQB / ISEB Foundation Exam Practice -1

Contents

Why testing is necessary

Fundamental test process

Psychology of testing

Re-testing and regression testing

Expected results

Prioritisation of tests

Principles

1 2 3

4 5 6

ISTQB / ISEB Foundation Exam Practice

Page 61: ISTQB / ISEB Foundation Exam Practice -1

Expected results

Should be predicted in advance as part of the test design process- ‘‘Oracle Assumption’ assumes that correct outcome can Oracle Assumption’ assumes that correct outcome can

be predicted.be predicted. Why not just look at what the software does and

assess it at the time?- subconscious desire for the test to pass - less work to do, subconscious desire for the test to pass - less work to do,

no incident report to write upno incident report to write up- it looks plausible, so it must be OK - less rigorous than it looks plausible, so it must be OK - less rigorous than

calculating in advance and comparingcalculating in advance and comparing

Page 62: ISTQB / ISEB Foundation Exam Practice -1

A test

A Program:

Source: Carsten Jorgensen, Delta, Denmark

inputsexpectedoutputs

3

8

6?

10?

Read AIF (A = 8) THEN PRINT (“10”)ELSE PRINT (2*A)

Page 63: ISTQB / ISEB Foundation Exam Practice -1

Contents

Why testing is necessary

Fundamental test process

Psychology of testing

Re-testing and regression testing

Expected results

Prioritisation of tests

Principles

1 2 3

4 5 6

ISTQB / ISEB Foundation Exam Practice

Page 64: ISTQB / ISEB Foundation Exam Practice -1

Prioritising tests

We can’t test everything There is never enough time to do all the

testing you would like So what testing should you do?

Page 65: ISTQB / ISEB Foundation Exam Practice -1

Most important principle

Prioritise tests

so that,

whenever you stop testing,

you have done the best testing

in the time available.

Prioritise tests

so that,

whenever you stop testing,

you have done the best testing

in the time available.

Page 66: ISTQB / ISEB Foundation Exam Practice -1

How to prioritise?

Possible ranking criteria (all risk based)- test where a failure would be most severetest where a failure would be most severe- test where failures would be most visibletest where failures would be most visible- test where failures are most likelytest where failures are most likely- ask the customer to prioritise the requirementsask the customer to prioritise the requirements- what is most critical to the customer’s businesswhat is most critical to the customer’s business- areas changed most oftenareas changed most often- areas with most problems in the pastareas with most problems in the past- most complex areas, or technically criticalmost complex areas, or technically critical

Page 67: ISTQB / ISEB Foundation Exam Practice -1

Summary: Key Points

Testing is necessary because people make errors

The test process: planning, specification, execution, recording, checking completion

Independence & relationships are important in testing

Re-test fixes; regression test for the unexpected

Expected results from a specification in advance

Prioritise to do the best testing in the time you have

Principles

1 2 3

4 5 6

ISTQB / ISEB Foundation Exam Practice