14

Click here to load reader

Software Testing Trainning - Day3

Embed Size (px)

Citation preview

Page 1: Software Testing Trainning - Day3

8/14/2019 Software Testing Trainning - Day3

http://slidepdf.com/reader/full/software-testing-trainning-day3 1/14

Testing Techniques & Levels of Testing Techniques & Levels of 

Testing.Testing.

Day 3-Session 1Lavanya.M

Page 2: Software Testing Trainning - Day3

8/14/2019 Software Testing Trainning - Day3

http://slidepdf.com/reader/full/software-testing-trainning-day3 2/14

Testing

Static Testing

Static testing, the review, inspection andvalidation of development requirements, is the most effective andcost efficient way of testing.

Dynamic TestingTesting that is commonly assumed to mean

executing software and finding errors is dynamic testing

Black Box Testing or Functional

White Box Testing or Structural

Page 3: Software Testing Trainning - Day3

8/14/2019 Software Testing Trainning - Day3

http://slidepdf.com/reader/full/software-testing-trainning-day3 3/14

Testing TechniquesTesting Techniques

Black Box Testing

White Box Testing

Page 4: Software Testing Trainning - Day3

8/14/2019 Software Testing Trainning - Day3

http://slidepdf.com/reader/full/software-testing-trainning-day3 4/14

White Box TechniquesWhite Box Techniques

Statement coverage : Execute each & everystatement of the code is called Statementcoverage.

Decision Coverage : Execute each decision

direction at least once

Conditional Coverage : Execute each & everycondition.

Loop coverage : Execute each & every loop.

Page 5: Software Testing Trainning - Day3

8/14/2019 Software Testing Trainning - Day3

http://slidepdf.com/reader/full/software-testing-trainning-day3 5/14

Black Box TestingBlack Box Testing

TechniquesTechniques

Equivalence Partitioning

Boundary Value Analysis

Error Guessing

Page 6: Software Testing Trainning - Day3

8/14/2019 Software Testing Trainning - Day3

http://slidepdf.com/reader/full/software-testing-trainning-day3 6/14

Equivalence partitioningEquivalence partitioning

Equivalence Partitioning: An approach where classes of inputs arecategorized for product or function validation. This usually does notinclude combinations of input, but rather a single state value based by

class. For example, with a given function there may be several classesof input that may be used for positive testing. If function expects aninteger and receives an integer as input, this would be considered aspositive test assertion. On the other hand, if a character or any otherinput class other than integer is provided, this would be considered anegative test assertion or condition.

E.g.: Verify a credit limit within a given range(1,000 – 2,000). Here we canidentify 3 conditions

1. < 1000

2. Between 1,000 and 2,000

3. >2000

Page 7: Software Testing Trainning - Day3

8/14/2019 Software Testing Trainning - Day3

http://slidepdf.com/reader/full/software-testing-trainning-day3 7/14

Techniques.Techniques.

Boundary Value Analysis

BVA is different from equivalence partitioning in that itfocuses on "corner cases" or values that are usually out ofrange as defined by the specification. This means that iffunction expects all values in range of negative 100 topositive 1000, test inputs would include negative 101 andpositive 1001. BVA attempts to derive the value often usedas a technique for stress, load or volume testing. This typeof validation is usually performed after positive functional

validation has completed (successfully) usingrequirements specifications and user documentation

Page 8: Software Testing Trainning - Day3

8/14/2019 Software Testing Trainning - Day3

http://slidepdf.com/reader/full/software-testing-trainning-day3 8/14

Age

BVA (Boundary Value Analysis )( Here we can define

for Size and Range)

Size: three

Range:

Min Pass

Min-1FailMin+1Pass

MaxPass

Max-1Pass

Max+1Fail

16 to 80

Page 9: Software Testing Trainning - Day3

8/14/2019 Software Testing Trainning - Day3

http://slidepdf.com/reader/full/software-testing-trainning-day3 9/14

Error GuessingBased on the Functionality, and the

experience of the Tester. They will have a

intuition.E.g.: Date Input – February 30, 2000Decimal Digit – 1.99.

Page 10: Software Testing Trainning - Day3

8/14/2019 Software Testing Trainning - Day3

http://slidepdf.com/reader/full/software-testing-trainning-day3 10/14

Levels of TestingLevels of Testing

Unit Testing

Integration Testing

System Testing

Acceptance Testing

Page 11: Software Testing Trainning - Day3

8/14/2019 Software Testing Trainning - Day3

http://slidepdf.com/reader/full/software-testing-trainning-day3 11/14

Unit TestingUnit Testing

Require knowledge of code

 – High level of detail

 – Deliver thoroughly tested components tointegration

Stopping criteria

 – Code Coverage

 – Quality

Page 12: Software Testing Trainning - Day3

8/14/2019 Software Testing Trainning - Day3

http://slidepdf.com/reader/full/software-testing-trainning-day3 12/14

Strategies

 – Bottom-up, start from bottom and add one ata time

 – Top-down, start from top and add one at a

time – Big-bang, everything at once

Simulation of other components

 – Stubs receive output from test objects – Drivers generate input to test objects

Integration TestingIntegration Testing

Page 13: Software Testing Trainning - Day3

8/14/2019 Software Testing Trainning - Day3

http://slidepdf.com/reader/full/software-testing-trainning-day3 13/14

Functional testing

 – Test end to end functionality, Testing againstcomplete requirement.

 – Requirement focus

• Test cases derived from specification

Use-case focus

• Test selection based on user profile

System TestingSystem Testing

Page 14: Software Testing Trainning - Day3

8/14/2019 Software Testing Trainning - Day3

http://slidepdf.com/reader/full/software-testing-trainning-day3 14/14

User (or customer) involvedEnvironment as close to field use aspossible

Focus on: – Building confidence

 – Compliance with defined acceptance

criteria in the contract

Acceptance TestingAcceptance Testing