definitions of software testing

8/18/2019 Definitions of Software Testing

1/6

Definitions of Software Testing -

• It is the process of Creating, Implementing and Evaluating tests.

• Testing measures software quality

• Testing can find faults. When they are removed, software quality is improved .

• Testing is executing a program with an indent of finding Error/Fault and Failure.

• IEEE Terminology : An examination of the ehavior of the program ! executing on sample data

sets.

Why is Software Testing Important?1. To discover defects.

2. To avoid user detecting prolems

3. To prove that the software has no faults

4. To learn aout the reliailit! of the software.

5. To avoid eing sued ! customers

6. To ensure that product wor"s as user expected.

7. To sta! in usiness

8. To detect defects earl!, which helps in reducing the cost of defect fixing#

Why start testing Early?

Introd!tion :$ou proal! heard and read in logs %Testing should start earl! in the life c!cle of development&. In thischapter, we will discuss "#y start testing Early$ ver! practicall!.

%a!t &ne'et(s start with the regular software development life c!cle)

*hen pro+ect is planned

• First we(ve got a planning phase) needs are expressed, people are contacted, meetings are

oo"ed. Then the decision is made) we are going to do this pro+ect.

• After that anal!sis will e done, followed ! code uild.


2/6

• ow it(s !our turn) !ou can start testing.

o !ou thin" this is what is going to happen# ream on.

This is whats going to happen)

This is what actual happened when the pro+ect executes

• lanning, anal!sis and code uild will ta"e more time then planned.

• That would not e a prolem if the total pro+ect time would pro-longer. Forget it0 it is most li"el!

that !ou are going to deal with the fact that !ou will have to perform the tests in a few da!s.

• The deadline is not going to e moved at all) promises have een made to customers, pro+ect

managers are going to lose their onuses if the! deliver later past deadline.

%a!t TwoThe earlier !ou find a ug, the cheaper it is to fix it.

rice of 1ugg! Code

If !ou are ale to find the ug in the re2uirements determination, it is going to e 34 times cheaper 5667 than when !ou find the same ug in testing.It will even e 844 times cheaper 5667 than when !ou find the ug after going live.


3/6

Eas! to understand) if !ou find the ug in the re2uirements definitions, all !ou have to do is change thetext of the re2uirements. If !ou find the same ug in final testing, anal!sis and code uild alread! too"place. 9uch more effort is done to uild something that nood! wanted.

'on!lsion: start testing early(This is what !ou should do)

Testing should e planned for each phase

• 9a"e testing part of each hase in the software life c!cle

• :tart test planning the moment the pro+ect starts

• :tart finding the ug the moment the re2uirements are defined

• ;eep on doing that during anal!sis and design phase

• 9a"e sure testing ecomes part of the development process

• And ma"e sure all test preparation is done efore !ou start final testing. If !ou have to start then,

!our testing is going to e crap6

*ant to "now how to do this#


4/6

• 1ehavior or performance ased errors.

• Initiali?ation or termination errors.

Methods of Black o! Testing

The following asic techni2ues are emplo!ed during lac" ox testing)

• E2uivalence Class

• 1oundar! @alue Anal!sis

• Error


5/6


6/6

Str!tre Testing:

• Condition Testing - All logical conditions contained in the program module should e tested.

• ata Flow Testing- :elects test paths according to the location of definitions and use of variales.

• 'oop Testing)

• :imple 'oops

• ested 'oops

• Concatenated 'oops

• >nstructured 'oops

/ray ,o0 Testing

• It is +ust a comination of oth 1lac" ox D white ox testing.

• It is platform independent and language independent.

• >sed to test emedded s!stems.

• Functionalit! and ehavioral parts are tested.

• Tester should have the "nowledge of oth the internals and externals of the function

• If !ou "now something aout how the product wor"s on the inside, !ou can test it etter from the

outside.

nless !ou

understand the architecture of the et, !our testing will e s"in deep.

definitions of software testing

Documents