Software testing
Download as PPTX, PDF2 likes431 views
This document provides an overview of software testing techniques. It discusses verification, validation, different testing levels including unit, integration and system testing. It also describes various testing techniques such as white box and black box testing. Specifically, it outlines verification as ensuring user expectations are met, validation as evaluating if a system meets its specifications, and different testing levels like unit, integration and system testing. It also summarizes white box testing as analyzing internal code and black box testing as evaluating external specifications without knowledge of internal workings.
Software testing
- 2. INTRODUCTION ï Testing refers to a defect detection mechanism and its purpose is to find errors. ï It is a process of executing a program with intent of finding an error.
- 3. VERIFICATION ï Verification is a process of determining whether or not the product of a given phase of software development fulfil the requirements established during the previous data. ï It means software product should meet user expectations, checking that users expectations are satisfied. ï We can do this with the help of Functional testing, Integration and interface testing, System testing, Acceptance criteria, Regression testing.
- 4. VALIDATION ï Validation is a process of evaluating a system or component during or at the end of development process to determine whether it satisfies the specified requirements. ï It ensures whether the software product is behaving according to its specification. ï We can do this with the help of Technical reviews and inspections, Root cause analysis, Metric definition, Certification demonstrations.
- 5. TESTING TECHNIQUES ï Testing is the process of execution of a program with the intent of finding errors. ï There are two types of testing techniques: 1. White box testing (Structural testing) 2. Black box testing (Functional testing)
- 6. WHITE BOX TESTING ï Testing based on the internal specification with knowledge of how system is constructed. ï In this testing approach, we have to analyse the code and use the knowledge about the program structure to derive test data. ï White box techniques are given below: 1. Basic path testing (Flow graph notation, Cyclomatic complexity, Graph metrics) 2. Control structure testing (Loop testing)
- 7. BLACK BOX TESTING ï Testing based on the external specification without the knowledge of how system is constructed. ï In this approach, testers need not to have explicit knowledge of internal workings of the item being tested. ï Black box techniques are given below: 1. Equivalence partition 2. Boundary value analysis 3. Robustness testing
- 8. LEVEL OF TESTING A software product goes through three levels of testing: 1. Unit testing 2. Integration testing 3. System testing
- 9. UNIT TESTING ï Unit testing is the process of taking a module (the smallest unit of software design) and running it in isolation from the rest of the software product by using prepared test cases and comparing the actual results with the results predicted by the specification and design of the module. ï It is white box oriented.
- 10. INTEGRATION TESTING ï Integration testing is used to test the integration and consistency of an integrated subsystem. ï It is applied incremently as modules are assembled into larger subsystems. ï It is done using a combination of both black box and white box testing techniques.
- 11. SYSTEM TESTING ï System testing focuses on complete integrated system to evaluate compliance with specified requirements. ï It is basically used for performance, stress and security testing. ï It includes techniques like Acceptance testing, Alpha and Beta testing, Performance testing, Regression testing
- 12. ACCEPTANCE TESTING ï Acceptance testing is performed before to handover the system to the customer. ï The customer may write the test criteria and request to the developer to execute them or the developer can write the criteria and take the customerâs approval. ï Acceptance testing focuses on complete integrated system to evaluate fitness of use.
- 13. ALPHA AND BETA TESTING ï Alpha testing is done at developerâs site by customer. ï In alpha testing, developers are present and environment is controlled. ï Beta testing is done at one or more customerâs site by end users/customers. ï In beta testing, we face live situation and here developer my or may not be present. ï Beta testing usually comes in picture when the number of users are millions.
- 14. PERFORMANCE TESTING ï Performance testing is concerned with assessing the time and memory aspects of the system ï It may be concerned with checking that the operation completes within the fixed deadline and only a fixed size of memory is allocated
- 15. REGRESSION TESTING ï Regression testing is applied after changes have been made to the system ï The operation of the new version is compared with the previous version to see, if there are any unexpected results
- 16. THANK YOU!!!