1. BY: GARIMA GUPTA MCA FINAL YEAR 0803314403

2. WHAT IS SOFTWARE TESTING ? SOFTWARE TESTING IS THE PROCESS OF EXECUTING PROGRAMS OR SYSTEM WITH THE INTENT OF FINDING ERORRS. SOFTWARE TESTING CAN ALSO BE STATED AS PROCEE OF VALIDATING AND VERIFYING THAT SOFTWARE PROGRAM/ APPLICATION MEETS THE BUSINESS AND TECHNICAL REQUIREMENT.

3. SCOPE OF TESTING Scope of software testing often includes examination of code as well as execution of that code in various environments and conditions. Scope of software testing often includes examination of code as well as execution of that code in various environments and conditions. It also examines the aspects of code: does it do, what it is supposed to do and do what it needs to do.

4. TESTING METHODS Software testing methods are traditionally divided into: WHITE BOX TESTING BLACK BOX TESTING GREY BOX TESTING

5. WHITE BOX TESTING White box testing is when the tester has access to the internal data structures and algorithms including the code that implement these. Types of white box testing : Types of white box testing : APIAPI APIs testing - testing of the application using public and private API Code coverageCode coverage - creating tests to satisfy some criteria of code coverage (e.g., the test designer can create tests to cause all statements in the program to be executed at least once) Code coverage Fault injectionFault injection methods - improving the coverage of a test by introducing faults to test code paths. Fault injection

6. BLACK BOX TESTING Black box testing treats the software as a" black box"—without any knowledge of internal implementation. Black box testing treats the software as a" black box"—without any knowledge of internal implementation. Black box testing methods include: Black box testing methods include: equivalence partitioning, equivalence partitioning,equivalence partitioningequivalence partitioning boundary value analysis, boundary value analysis,boundary value analysisboundary value analysis model-based testing. model-based testing.model-based testingmodel-based testing

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

8. TESTING LEVELS Tests are frequently grouped by the level of specificity of the tests. Tests are frequently grouped by the level of specificity of the tests. The main levels during the development process are: The main levels during the development process are: UNIT TESTING SYSTEM TESTING INTEGRATION TESTING

9. UNIT TESTING : Unit testing refers to tests that verify the functionality of a specific section of code, usually at the function level. INTEGRATION TESTING :Integration testing is any type of software testing that seeks to verify the interfaces between components against a software design. SYSTEM TESTING : System testing tests a completely integrated system to verify that it meets its requirements

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

11. HAVE A NICE AND WODERFUL DAY