Learn software testing with tech partnerz 1
1 like•684 views
This document outlines a training program on software testing provided by TechPartnerz. It discusses key concepts like verification and validation, provides details on various testing strategies and methodologies including requirements review, unit testing, integration testing and more. It also covers establishing a software testing framework, considering factors like project type, scope, risks. Testing should occur throughout the software development lifecycle from requirements to installation. Both functional and structural testing approaches are important.
Learn software testing with tech partnerz 1
- 1. Learn Software Testing With TechPartnerz Session 1 http://www.techpartnerz.com
- 2. Your Partner for Professional Successhttp://www.techpartnerz.com In this presentation….. What is Verification & Validation? Session 1 Verification Strategies. Validation Strategies. Establishing a Software Testing Methodology. Test Phases. Session 2 Metrics. Configuration Management. Session 3 Test Development. Defect Tracking Process. Deliverables.
- 3. Your Partner for Professional Successhttp://www.techpartnerz.com What is Verification & Validation? Verification and Validation are the basic ingredients of Software Quality Assurance (SQA) activities. “Verification” checks whether we are building the right system, and “Validation” checks whether we are building the system right.
- 4. Your Partner for Professional Successhttp://www.techpartnerz.com Verification Strategies comprise of the following: 1. Requirements Review. 2. Design Review. 3. Code Walkthrough. 4. Code Inspections. Verification Strategies
- 5. Your Partner for Professional Successhttp://www.techpartnerz.com Validation Strategies comprise of the following: 1. Unit Testing. 2. Integration Testing. 3. System Testing. 4. Performance Testing. 5. Alpha Testing. 6. User Acceptance Testing (UAT). 7. Installation Testing. 8. Beta Testing. Validation Strategies
- 6. Your Partner for Professional Successhttp://www.techpartnerz.com Verification Strategies…in detail Verification Strategy Explanation Deliverable Requirements Review The study and discussions of the computer system requirements to ensure they meet stated user needs and are feasible. Reviewed statement of requirements. Design Review The study and discussion of the computer system design to ensure it will support the system requirements. System Design Document, Hardware Design Document. Code Walkthrough Informal analysis of the program source code to find defects and verify coding techniques. Software ready for initial testing by the developer. Code Inspection Formal analysis of the program source code to find defects as defined by meeting system design specification. Software ready for testing by the testing team.
- 7. Your Partner for Professional Successhttp://www.techpartnerz.com Validation Strategies…in detail Validation Strategy Explanation Deliverable Unit Testing Testing of single program, modules, or unit of code. Software unit ready for testing with other system component. Integration Testing Testing of related programs, modules, or units of code. Portions of the system ready for testing with other portions of the system. System Testing Testing of entire computer system. This kind of testing can include functional and structural testing. Tested computer system, based on what was specified to be developed. Performance Testing Testing of the application for the performance at stipulated times and stipulated number of users. Stable application performance.
- 8. Your Partner for Professional Successhttp://www.techpartnerz.com Validation Strategies…in detail Validation Strategy Explanation Deliverable Alpha Testing Testing of the whole computer system before rolling out to the UAT. Stable application. User Acceptance Testing (UAT) Testing of computer system to make sure it will work in the system regardless of what the system requirements indicate. Tested and accepted system based on the user needs. Installation Testing Testing of the Computer System during the Installation at the user place. Successfully installed application. Beta Testing Testing of the application after the installation at the client place. Successfully installed and running application.
- 9. Your Partner for Professional Successhttp://www.techpartnerz.com In order to establish software testing methodology and developing the framework for developing the testing tactics, the following eight considerations should be described: Acquire and study the Test Strategy. Determine the Type of Development project. Determine the Type of Software System. Determine the project scope. Identify the tactical risks. Determine when testing should occur. Build the system test plan. Build the unit test plan. Establishing a Software Testing Methodology.
- 10. Your Partner for Professional Successhttp://www.techpartnerz.com Type of Development Project Type Characteristics Test Tactic Traditional System Development •Uses a system development methodology. •User knows requirements. •Development determines structure. •Test at end of each task/step/phase. •Verify that specs match need. •Test function and structure. Iterative development / Prototyping / CASE •Requirements unknown. •Structure pre-defined. •Verify that CASE tools are used properly. •Test functionality. System Maintenance •Modify structure. •Test structure. •Works best with release methods. •Requires regression testing. Purchased / Contracted Software •Structure unknown. •May contain defects. •Functionality defined in user documentation. •Documentation may vary from software. •Verify that functionality matches need. •Test functionality. •Test fit into environment.
- 11. Your Partner for Professional Successhttp://www.techpartnerz.com Testing can and should occur throughout the phases of a project. Requirements Phase • Determine the test strategy. • Determine adequacy of requirements. • Generate functional test conditions. Design Phase • Determine consistency of design with requirements. • Determine adequacy of design. • Generate structural and functional test conditions. Program (Build) Phase • Determine consistency with design. • Determine adequacy of implementation. • Generate structural and functional test conditions for programs/units. When Testing should occur..?
- 12. Your Partner for Professional Successhttp://www.techpartnerz.com Test Phase • Determine adequacy of the test plan. • Test application system. Installation Phase • Place tested system into production. Maintenance Phase • Modify and retest. When Testing should occur..?
- 13. Your Partner for Professional Successhttp://www.techpartnerz.com Two types of testing can be taken into consideration. Functional or Black Box Testing. Structural or White Box Testing. Functional testing ensures that the requirements are properly satisfied by the application system. The functions are those tasks that the system is designed to accomplish. Structural testing ensures sufficient testing of the implementation of a function. Types of Testing.
- 14. Your Partner for Professional Successhttp://www.techpartnerz.com Structural Testing. Technique Explanation Example Stress Determine system performance with expected volumes. Sufficient disk space allocated. Execution System achieves desired level of proficiency. Transaction turnaround time adequate. Recovery System can be returned to an operational status after a failure. Evaluate adequacy of backup data.
- 15. Your Partner for Professional Successhttp://www.techpartnerz.com Structural Testing. Technique Explanation Example Operations System can be executed in a normal operational status. Determine systems can run using document. Compliance System is developed in accordance with standards and procedures. Standards follow. Security System is protected in accordance with importance to organization. Access denied.
- 16. Your Partner for Professional Successhttp://www.techpartnerz.com Functional Testing. Technique Explanation Example Requirements System performs as specified. Prove system requirements. Regression Verifies that anything unchanged still performs correctly. Unchanged system segments function. Error Handling Errors can be prevented or detected and then corrected. Error introduced into the test.
- 17. Your Partner for Professional Successhttp://www.techpartnerz.com Functional Testing. Technique Explanation Example Manual Support The people-computer interaction works. Manual procedures developed. Inter Systems Data is correctly passed from system to system. Intersystem parameters changed. Control Controls reduce system risk to an acceptable level. File reconciliation procedures work. Parallel Old systems and new system are run and the results compared to detect unplanned differences. Old and new system can reconcile.
- 18. Your Partner for Professional Successhttp://www.techpartnerz.com End of session 1
- 19. Your Partner for Professional Successhttp://www.techpartnerz.com About TechPartnerz TechPartnerz is an IIT NIT alumni company providing end to end IT training solutions to Corporates, working professionals and Freshers TechPartnerz provides certification training programs for ITIL-Foundation, ITIL-Intermediate, PRINCE2-Foundation, PRINCE2-Practitioner, COBIT 5, Cloud Computing etc Our Software Training Portfolio includes training on QTP, Selenium, Loadrunner, Jmeter, SoapUI etc.
- 20. Your Partner for Professional Successhttp://www.techpartnerz.com Thank You For any queries feel free to contact TechPartnerz [email protected] Follow TechPartnerz on facebook, Linkedin, twitter