Software Testing

TEST PLAN TEMPLATE IEEE 829 1) Test Plan Identifier 2) References 3) Introduction 4) Test Items 5) Software Risk Issues 6) Features to be Tested 7) Features not to be Tested 8) Approach 9) Item Pass/Fail Criteria 10) Suspension Criteria and Resumption Requirements 11)  Test Deliverables 12) Remaining Test Tasks 13) Environmental Needs 14) Staffing and Training Needs 15) Responsibilities 16) Schedule 17) Planning Risks and Contingencies 18) Approvals 19) Glossary

High Severity – High Priority bug This is when major path through the application is broken, for example, on an eCommerce website, every customers get error message on the booking form and cannot place orders, or the product page throws a Error of page not found. High Severity – Low Priority bug This happens when the bug causes major problems, but it only happens in very rare conditions or situations, for example, customers who use very old browsers cannot continue with their purchase of a product. Because the number of customers with very old browsers is very old version, it is not a high priority to fix the issue. High Priority – Low Severity bug The logo or name of the company is not displayed on the website. It is important to fix the issue as soon as possible, although it may not create cause a System and other component. Low Priority – Low Severity bug The privacy policy page take a long time to load. Not many people view the privacy policy page and slow...