Scribd
Upload
12 views

Session 3

Uploaded by

emmnslivsstil
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
12 views

Session 3

Uploaded by

emmnslivsstil
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 18

SESSION 3

WWW.PAVANONLINETRAININGS.COM
QA Vs QC

• QA is Process related.
• QC is the actual testing of the software.
• QA focuses on building in quality.
• QC focuses on testing for quality.
• QA is preventing defects.
• QC is detecting defects.
• QA is process oriented.
• QC is Product oriented.
• QA for entire life cycle.
• QC for testing part in SDLC

WWW.PAVANONLINETRAININGS.COM
Testing Methodologies

▪ White Box Testing


▪ Black Box Testing
▪ Grey Box Testing

WWW.PAVANONLINETRAININGS.COM
White Box Testing

▪ White Box Testing conducts on internal logic of the programs.


▪ Programming Skills are required.
▪ Ex: Unit Testing & Integration Testing

WWW.PAVANONLINETRAININGS.COM
Black Box Testing

▪ Testing conducts on functionality of the application whether it is working according to


customer requirements or not.

▪ Ex: System Testing & UAT Testing

WWW.PAVANONLINETRAININGS.COM
Grey Box Testing

▪ Both combination of white box and black box testing.


▪ Ex: Database Testing

WWW.PAVANONLINETRAININGS.COM
Levels Of Testing

1) Unit Testing
2) Integration Testing
3) System Testing
4) UAT Testing

WWW.PAVANONLINETRAININGS.COM
Unit Testing

• A unit is a single component or module of a software.


• Unit testing conducts on a single program or single module.

• Unit Testing is white box testing technique.


• Unit testing is conducted by the developers.
• Unit testing techniques:
• Basis path testing
• Control structure testing
• Conditional coverage
• Loops Coverage
• Mutation Testing

WWW.PAVANONLINETRAININGS.COM
Integration Testing

▪ Integration testing performed between 2 or more


modules.

▪ Integration testing focuses on checking data


communication between multiple modules.
▪ Integrated Testing is white box testing technique.
▪ Example:

WWW.PAVANONLINETRAININGS.COM
Integration Testing Types

▪ Incremental Integration Testing


▪ Non- Incremental Testing

WWW.PAVANONLINETRAININGS.COM
Incremental Integration

▪ Incremental Integration : Incrementally adding the modules and testing the data flow
between the modules.

▪ There 3 Approaches
– Top Down
– Bottom Up
– Hybrid(sandwich)

WWW.PAVANONLINETRAININGS.COM
Incremental Integration (Top down Integration)

▪ Incrementally adding the modules and testing the data flow between the modules.
▪ Ensure the module added is the child of previous module.
• Takes help of stubs for testing.

Child of Module1

Child of Module2

WWW.PAVANONLINETRAININGS.COM
Incremental Integration(Bottom-Up Integration)

• Incrementally adding the modules and testing the data flow between the modules.
• Ensure the module added is the parent of the previous module.

Parent of Module2

Parent of Module1

WWW.PAVANONLINETRAININGS.COM
Incremental Integration (Sandwich/Hybrid Approach)

▪ Combination of Top-Down & Bottom Up approach is called Sandwich Approach.

WWW.PAVANONLINETRAININGS.COM
Non- Incremental Integration Testing/Big Bang Testing

▪ Adding all the modules in a single shot and test the data flow between modules.
▪ Drawbacks:
– We might miss data flow between some of the modules.
– If you find any defect we cant understand the root cause of defect.

WWW.PAVANONLINETRAININGS.COM
Integration Testing – Stubs & Drivers

▪ Stubs and Drivers are the dummy programs in Integration testing used to facilitate the
software testing activity. These programs act as a substitutes for the missing models in the
testing. They do not implement the entire programming logic of the software module but
they simulate data communication with the calling module while testing.
▪ Stub: Is called by the Module under Test.
▪ Driver: Calls the Module to be tested.

WWW.PAVANONLINETRAININGS.COM
System Testing

▪ Testing over all functionality of the application with respective client requirements.
▪ It is a black box testing technique.
▪ This testing is conducted by testing team.
▪ After completion of component and integration level testing’s we start System testing.
▪ Before conducting system testing we should know the customer requirements.
▪ System Testing focusses on below aspects.
– User Interface Testing (GUI)
– Functional Testing
– Non-Functional Testing
– Usability Testing

WWW.PAVANONLINETRAININGS.COM
User Acceptance Testing (UAT)

• After completion of system testing UAT team conducts acceptance testing in two levels.
• Alpha testing
• Beta testing

WWW.PAVANONLINETRAININGS.COM

You might also like