More Related Content
What's hot
What's hot (20)
Similar to Software testing
Similar to Software testing (20)
Recently uploaded
Recently uploaded (20)
Software testing
- 2. CONTENT • Introduction • What is Software Testing ? • benefits of Software TestingGoals of Testing • Testing Strategies in Software Engineering • Types of Software Testing • Testing Methodology • Software Testing lifecycle - Phases • Types of Performance Testing • Reviews, Inspections, and Walkthroughs • Conclusion
- 3. INTRODUCTION • Software Testing is a method to check whether the actual software product matches expected requirements and to ensure that software product is Defect free. It involves execution of software/system components using manual or automated tools to evaluate one or more properties of interest. The purpose of software testing is to identify errors, gaps or missing requirements in contrast to actual requirements.
- 4. BENEFITS OF SOFTWARE TESTING • cost-Effective: It is one of the important advantages of software testing. Testing any IT project on time helps you to save your money for the long term. In case if the bugs caught in the earlier stage of software testing, it costs less to fix. • Security: It is the most vulnerable and sensitive benefit of software testing. People are looking for trusted products. It helps in removing risks and problems earlier. • Product quality: It is an essential requirement of any software product. Testing ensures a quality product is delivered to customers. • Customer Satisfaction: The main aim of any product is to give satisfaction to their customers. UI/UX Testing ensures the best user experience.
- 5. TESTING STRATEGIES IN SOFTWARE ENGINEERING • Unit Testing: This software testing basic approach is followed by the programmer to test the unit of the program. It helps developers to know whether the individual unit of the code is working properly or not. • Integration testing: It focuses on the construction and design of the software. You need to see that the integrated units are working without errors or not. • System testing: In this method, your software is compiled as a whole and then tested as a whole. This testing strategy checks the functionality, security, portability, amongst others.
- 6. TYPES OF SOFTWARE TESTING • Functional Testing • Non-Functional Testing or Performance Testing • Maintenance (Regression and Maintenance)
- 7. TESTING METHODOLOGIES • White box testing • Black-box testing
- 8. • White box testing Knowledge of the internal program design and code required. Tests are based on coverage of code statements, branches, paths, conditions. • Black box testing No knowledge of internal program design or code required. Tests are based on requirements and functionality.
- 10. SOFTWARE TESTING LIFECYCLE - PHASES • Requirements study • Test Case Design and Development • Test Execution • Test Closure • Test Process Analysis
- 11. REQUIREMENTS STUDY • Testing Cycle starts with the study of client’s requirements. • Understanding of the requirements is very essential for testing the product.
- 12. ANALYSIS & PLANNING • Test objective and coverage • Overall schedule • Standards and Methodologies • Resources required, including necessary training • Roles and responsibilities of the team members • Tools used
- 13. Test Case Design and Development •Component Identification •Test Specification Design •Test Specification Review Test Execution •Code Review •Test execution and evaluation •Performance and simulation
- 14. Test Closure • Test summary report • Project De-brief • Project Documentation Test Process Analysis Analysis done on the reports and improving the application’s performance by implementing new technology and additional features.
- 15. TYPES OF PERFORMANCE TESTING Stress Testing Volume Testing Configuration Testing Compatibility Testing Regression Testing Recovery Testing Maintenance Testing Documentation Testing Usability Testing
- 16. CONCLUSION In order to be cost effective, the testing must be concentrated on areas where it will be most effective. The testing should be planned such that when testing is stopped for whatever reason, the most effective testing in the time allotted has already been done. The absence of an organizational testing policy may result in too much effort and money will be spent on testing, attempting to achieve a level of quality that is impossible or unnecessary.
- 17. REVIEWS, INSPECTIONS, AND WALKTHROUGHS • In a review (also called a technical review), a work product is examined for defects by individuals other than the person who produced it. A work product is any important deliverable created during the requirements, design, coding, or testing phase of software development. Examples of work products are project charters, phase plans, requirements models, requirements and design specifications, user interface prototypes, source code, architectural models, user documentation, and test scripts.
- 18. REVIEWS, INSPECTIONS, AND WALKTHROUGHS • An inspection is the most formal type of group review. Roles (producer, moderator, reader and reviewer, and recorder) are well defined, and the inspection process is prescribed and systematic. For example, reviewers might first attend an orientation meeting, after which they individually desk-check the product (carefully examine it on their own). At the inspection meeting itself, someone other than the producer of the work product runs the meeting. During the meeting, participants use a checklist (discussed shortly) to review the product one portion at a time. Issues and defects are recorded, and a product disposition is determined. When the product needs rework, another inspection might be needed to verify the changes.
- 19. REVIEWS, INSPECTIONS, AND WALKTHROUGHS • In a walkthrough, the producer describes the product and asks for comments from the participants. These gatherings generally serve to inform participants about the product rather than correct it.
- 20. Thanks