demian-3724-software-testing-qa-quality-assurance-product-education-ppt-powerpoint

8/7/2019 Demian-3724-software-testing-qa-quality-assurance-product-education-ppt-powerpoint

1/14

1

The Importance of Software Testing


2/14

2

A Necessary Evil

All project managers know that they mustdo some testing

The basic questions are;How much?What sort?By whom?

When and by when?

All difficult questions.


3/14

3

Why do we test?

Provide confidence in the systemIdentify areas of weaknessEstablish the degree of quality

Establish the extent that the requirements havebeen met, i.e. what the users asked for is whatthey got not what someone else though theywantedTo provide an understanding of the overall systemTo prove it is both usable and operableTo provide sufficient information to allow anobjective decision on applicability to deploy


4/14

4

Another view cynical?

To use up spare budget To provide a good excuse why the project is

lateTo provide jobs for people who cant codeTo make the developers look good To provide the project manager with somecontingency in the plan and can be cut if if

push come to shove!


5/14


6/14

6

How do we decide?

What matters to our users?What does the system do?RiskRequirementsMoney

Test Techniques - CoverageStaticDynamic


7/14

7

Secondly What sort?

UnitInterface

FunctionalityPerformanceUsability

SecurityAvailabilityOperability

plus about another

20 abilities


8/14

8

Do we need tools to help?

Automated test tools are often seen as a silverbullet

Some tests cannot be successfully executed oranalysed without them

80% of test tools end up as shelfware through:AbandonmentNeglectBanishment


9/14

9

Thirdly By whom?

Users: those who will ultimately use thesystem

Customers: those who define the system are they the same as the users?

TestersAnalystsDevelopers


10/14

10

Are we capable of testing?

Is an experienced tester better than anexperienced user at finding faults?

How can testers help themselves and users?Working with the users to understand theirsystemsProviding testing skills transferAttending testing industry conferencesAttaining industry recognised software testingqualifications


11/14

11

Lastly When?

Once the code is complete?As soon as the architecture is defined?

Once the system delivery is complete?During development?Once the business requirements have beendefined?As soon as the project is given the go-ahead?


12/14


13/14

13

Project deadline driven by:LegislationArbitrary dateFinancial yearCalendar dateSeasonal

Marketing windowSafety CriticalityMoney

By when?


14/14

14

Summary

Testing is an integral part of the system developmentfunction, not an afterthought:

Testing starts with the requirements not the codeTesting is a static and dynamic activityPrevention is better than cureThe sooner you find the fault the cheaper it is to fixCreate re-usable testware Process first then toolsNot everyone can test well, use professional testersPlanned testing in a controlled environment providesobjective metrics

To gain a Return on Investment you must first Invest

demian-3724-software-testing-qa-quality-assurance-product-education-ppt-powerpoint

Documents