BY:BY:

GARIMA GUPTAGARIMA GUPTA

MCA FINAL YEARMCA FINAL YEAR

08033144030803314403

WHAT IS SOFTWARE TESTING ?WHAT IS SOFTWARE TESTING ?

SOFTWARE TESTING IS THE PROCESS OF SOFTWARE TESTING IS THE PROCESS OF EXECUTING PROGRAMS OR SYSTEM WITH EXECUTING PROGRAMS OR SYSTEM WITH THE INTENT OF FINDING ERORRS.THE INTENT OF FINDING ERORRS.

SOFTWARE TESTING CAN ALSO BE SOFTWARE TESTING CAN ALSO BE STATED AS PROCEE OF VALIDATING AND STATED AS PROCEE OF VALIDATING AND VERIFYING THAT SOFTWARE PROGRAM/ VERIFYING THAT SOFTWARE PROGRAM/ APPLICATION MEETS THE BUSINESS AND APPLICATION MEETS THE BUSINESS AND TECHNICAL REQUIREMENT.TECHNICAL REQUIREMENT.

SCOPE OF TESTINGSCOPE OF TESTING

Scope of software testing often Scope of software testing often includes examination of code as well includes examination of code as well as execution of that code in various as execution of that code in various environments and conditions.environments and conditions.

It also examines the aspects of code: It also examines the aspects of code: does it do, what it is supposed to do does it do, what it is supposed to do and do what it needs to doand do what it needs to do . .

TESTING METHODSTESTING METHODS

Software testing methods are Software testing methods are traditionally divided into:traditionally divided into:

WHITE BOX TESTINGWHITE BOX TESTING

BLACK BOX TESTINGBLACK BOX TESTING

GREY BOX TESTINGGREY BOX TESTING

WHITE BOX TESTINGWHITE BOX TESTINGWhite box testingWhite box testing is when the tester has access to the is when the tester has access to the

internal data structures and algorithms including the internal data structures and algorithms including the code that implement these. code that implement these.

Types of white box testingTypes of white box testing : :

API APIs testing - testing of the application using APIs testing - testing of the application using public and private public and private

Code coverage - creating tests to satisfy some - creating tests to satisfy some criteria of code coverage (e.g., the test designer can criteria of code coverage (e.g., the test designer can create tests to cause all statements in the program create tests to cause all statements in the program to be executed at least once) to be executed at least once)

Fault injection methods - improving the coverage of a methods - improving the coverage of a test by introducing faults to test code paths.test by introducing faults to test code paths.

BLACK BOX TESTINGBLACK BOX TESTING

Black box testing treats the software as Black box testing treats the software as a" black box"—without any knowledge a" black box"—without any knowledge of internal implementation.of internal implementation.

Black box testing methods includeBlack box testing methods include::

equivalence partitioning,equivalence partitioning,

boundary value analysis, boundary value analysis,

model-based testing.model-based testing.

GREY BOX TESTINGGREY BOX TESTING

Grey box testingGrey box testing involves having involves having knowledge of internal data structures and knowledge of internal data structures and algorithms for purposes of designing the algorithms for purposes of designing the test cases, but testing at the user, or test cases, but testing at the user, or black-box level .black-box level .

TESTING LEVELSTESTING LEVELS

Tests are frequently grouped by the Tests are frequently grouped by the level of specificity of the tests.level of specificity of the tests.

The main levels during the development The main levels during the development process areprocess are: :

UNIT TESTINGUNIT TESTING

SYSTEM TESTING SYSTEM TESTING

INTEGRATION TESTINGINTEGRATION TESTING

UNIT TESTING :UNIT TESTING : Unit testing refers to tests Unit testing refers to tests that verify the functionality of a specific that verify the functionality of a specific section of code, usually at the function level.section of code, usually at the function level.

INTEGRATION TESTING :INTEGRATION TESTING :Integration testing Integration testing is any type of software testing that seeks to is any type of software testing that seeks to verify the interfaces between components verify the interfaces between components against a software design.against a software design.

SYSTEM TESTING : SYSTEM TESTING : System testing tests a System testing tests a completely integrated system to verify that it completely integrated system to verify that it meets its requirements meets its requirements

OBJECTIVE OF TESTINGOBJECTIVE OF TESTINGRegression testingRegression testing focuses on finding defects after a focuses on finding defects after a major code change has occurred. Specifically, it seeks to major code change has occurred. Specifically, it seeks to uncover old bugs that have come back. Such regressions uncover old bugs that have come back. Such regressions occur whenever software functionality that was previously occur whenever software functionality that was previously working correctly stops working as intended. working correctly stops working as intended. Acceptance testingAcceptance testing is performed by the customer, often in is performed by the customer, often in their lab environment on their own hardware .their lab environment on their own hardware .Alpha testingAlpha testing is simulated or actual operational testing by is simulated or actual operational testing by potential users/customers or an independent test team at potential users/customers or an independent test team at the developer’s site .the developer’s site .Beta testingBeta testing comes after alpha testing and can be comes after alpha testing and can be considered a form of external user acceptance testing. considered a form of external user acceptance testing. Versions of the software, known as beta versions, are Versions of the software, known as beta versions, are released to a limited audience outside of the programming released to a limited audience outside of the programming team team

HAVE A NICE AND HAVE A NICE AND WODERFUL DAYWODERFUL DAY