1. Software Testing By Marcin Starzomski :P

2. What is Testing ? Testing is a process used to help identify the correctness, completeness and quality of developed computer software. Testing is nothing but criticism or comparison, that is comparing the actual value with expected one. Testing is a process used to help identify the correctness, completeness and quality of developed computer software. Testing is nothing but criticism or comparison, that is comparing the actual value with expected one.

3. Ssoftware faults and Software failures failure - the software does not do what the user expects failure - the software does not do what the user expects faults - error in the correctness of the semantic of a computer program faults - error in the correctness of the semantic of a computer program

4. White box(glass box) Testing In white box or "glass box", testing the test developer has access to the source code. They ensure that components used in the construction are functional to some degree. In white box or "glass box", testing the test developer has access to the source code. They ensure that components used in the construction are functional to some degree.

5. Black box Testing In black box testing the test engineer only accesses the software through the same interfaces that the customer or user would. In black box testing the test engineer only accesses the software through the same interfaces that the customer or user would.

6. Grey (Gray) Box Testing The typical grey box tester is permitted to set up or manipulate the testing environment. It can also be used of testers who know the internal workings or algorithm of the software under test and can write tests specifically for the anticipated results. The typical grey box tester is permitted to set up or manipulate the testing environment. It can also be used of testers who know the internal workings or algorithm of the software under test and can write tests specifically for the anticipated results.

7. ALFA Testing Phase In the first phase of alpha testing, developers test the software using white box techniques. Additional inspection is then performed using black box or grey box techniques. In the first phase of alpha testing, developers test the software using white box techniques. Additional inspection is then performed using black box or grey box techniques.

8. BETA Testing Phase Versions of the software, known as beta- versions, are released to a limited audience outside of the company. Testing during the beta phase, informally called 'beta testing, is generally constrained to black box techniques although a core of test engineers are likely to continue with white box testing in parallel to the beta tests. Versions of the software, known as beta- versions, are released to a limited audience outside of the company. Testing during the beta phase, informally called 'beta testing, is generally constrained to black box techniques although a core of test engineers are likely to continue with white box testing in parallel to the beta tests.

9. GAMMA Testing Phase :] Cynics have referred to all software releases as "gamma testing" since defects are found in almost all commercial, commodity and publicly available software eventually Cynics have referred to all software releases as "gamma testing" since defects are found in almost all commercial, commodity and publicly available software eventually

10. Remember ! Alpha and beta refer to stages of the software before release (and also implicitly on the size of the testing community, and the constraints on the testing methods), white box, black box, and grey box refer to the ways in which the tester accesses the target. Alpha and beta refer to stages of the software before release (and also implicitly on the size of the testing community, and the constraints on the testing methods), white box, black box, and grey box refer to the ways in which the tester accesses the target.

11. Cycle of testing Requirements Analysis: Testing should begin in the requirements phase of the software life cycle(SDLC). Requirements Analysis: Testing should begin in the requirements phase of the software life cycle(SDLC). Design Analysis: During the design phase, testers work with developers in determining what aspects of a design are testable and under what parameter those testers work. Design Analysis: During the design phase, testers work with developers in determining what aspects of a design are testable and under what parameter those testers work. Test Planning: Test Strategy Test Planning: Test Strategy Test Development: Test Scenarios, Test Cases, Test Scripts to use in testing software. Test Development: Test Scenarios, Test Cases, Test Scripts to use in testing software. Test Execution: Testers execute the software based on the plans and tests and report any errors found to the development team. Test Execution: Testers execute the software based on the plans and tests and report any errors found to the development team. Test Reporting: Once testing is completed, testers generate metrics and make final reports on their test effort and whether or not the software tested is ready for release. Test Reporting: Once testing is completed, testers generate metrics and make final reports on their test effort and whether or not the software tested is ready for release. Retesting the Defects Retesting the Defects

12. System testing Most software produced today is modular. System testing is a phase of software testing in which developers see if there are any communications flaws--either not passing information, or passing incorrect information-- between modules. Most software produced today is modular. System testing is a phase of software testing in which developers see if there are any communications flaws--either not passing information, or passing incorrect information-- between modules.

13. Code Coverage Code coverage is inherently a white box testing activity.process allows developers and quality assurance personnel to look for parts of a system that are rarely or never accessed under normal conditions (error handling and the like) and helps reassure test engineers that the most important conditions (function points) have been tested. Code coverage is inherently a white box testing activity.process allows developers and quality assurance personnel to look for parts of a system that are rarely or never accessed under normal conditions (error handling and the like) and helps reassure test engineers that the most important conditions (function points) have been tested. process allows developers and quality assurance personnel to look for parts of a system that are rarely or never accessed under normal conditions (error handling and the like) and helps reassure test engineers that the most important conditions (function points) have been tested. process allows developers and quality assurance personnel to look for parts of a system that are rarely or never accessed under normal conditions (error handling and the like) and helps reassure test engineers that the most important conditions (function points) have been tested.

14. Testing Dilema Exploratory vs. Scripted Exploratory vs. Scripted Manual vs. Automated Manual vs. Automated

15. Thank you For paying atention to the end of teh presentation ! Thank you For paying atention to the end of teh presentation !