Software testing implementation
1 like5,244 views
This document discusses key considerations for software testing implementation including determining the appropriate quality standard based on the software's application and potential damages from failure. It also addresses determining the testing strategy such as using an incremental or "big bang" approach. Specific parts of the testing plan that should use white box or automated testing are to be defined. The document outlines planning test cases, designing test procedures and cases, implementing tests, and generating a software test report.
Software testing implementation
- 1. SOFTWARE TESTING IMPLEMENTATION LUTHFIYA ULINNUHA - 5209100115
- 2. MAIN ISSUES The appropriate required software quality standard The software testing strategy.
- 4. • Determining the test methodology The level of quality standard selected for a project depends mainly on the characteristics of the software’s application. the evaluation of the nature and magnitude of expected damages in case of system failure
- 5. • Typical damage to customer and user
- 7. Determining te software testing ■ The testing strategy: should a big bang or incremental testing strategy be adopted? If incremental testing is preferable, should testing be performed bottom-up or top-down? ■ Which parts of the testing plan should be performed according to the white box testing model? ■ Which parts of the testing plan should be performed according to the automated testing model?
- 8. • Planning test Test to be planned - Unit tests - Integration tests - System tests. Test planning documentation with “STP” or software test plan
- 9. SOFTWARE TEST PLAN TEMPLATE • Scope of test • Testing enviromenment • Test detail (for each test) • Testschedule (for each testor testgroup) including time estimates
- 10. • Test Design - Detailed design and procedures for each test - Test case database/file.
- 12. The output is software test resport or “STR” that include in - Test identification, site, schedule and participation - Test environment - Summary tables for total number of errors, their distribution and types - Special events and testers’ proposals