We will perform the testing activities in step by step systematic manner. Following are the main set of activities performed during testing life cycle.
- 1.Understand Project Summary
- 2.Understand the Business Requirements and Functional Requirements
- 3.Estimation of time and resources required
- 4.Prepare Test Plan
- 5.Write the Test scenarios
- 6.Write Test Cases and RTM
- 7.Review Test Cases
- 8.Test Environment Setup and Build Deployment
- 9.Test Execution, Bug Reporting and Tracking
- 10.Sanity Testing, Re-Testing and Regression Testing
- 11.Test Sign off/Test Closure/Test Summary Report
Project Summary:
It is an e-commerce application/product. It has various features like Registration, Login, Browse/search the products ,Add the products to cart, Perform payment, Product shipment tracking, Initiate Product Return and many more.
Application has 2 mains areas:
A) Front-end for end users/customers
Activities at front end:
- Login
- Browse/search the products
- Add the products to cart
- Perform payment
- Product shipment tracking
- Initiate Product Return and Many more....
B) Back-end for admin access for managing the e-commerce platform
Activities at back end:
- Add product
- Remove product
- Change product price
- Refund Many more....
For this project our Testing Focus Area is to test the front end of the application from the end user/customer perspective.
Application to be tested - https://demo.opencart.com/ ,we will deploy this application at local host and perform testing.
Testing Documents:
BRS, FRS, Use Cases and other supporting documents : These documents are prepared by the Business Analysts or Product Managers in consultation with the relavant stakeholders. These documents contain detailed business and functional requirements. While preparing test scenarios and test cases, if any requirements are not clear then we can raise query to document owner.
Test Plan: Test plan is a document that provides details about the scope of testing, testing environment, resources requried for testing, test schedule, entry and exit criteria, suspensiona and resumption criteria etc.
Test Scenarios: Test scenarios describe the functionality or an area of an application to be tested.
Test Cases: Test cases are created using test scenarios, one test scenario can have multiple test cases. Test case provides sequence of steps for test execution along with pre-condition, post-condition, Test data, Expected Result, Actual Result and Test Result etc.
Test Environment Setup: Every project needs certian type of environments and tools to perform the text execution, For this project we setup test environment using XAMPP which privdes Apache web server, MySQL and PHP as a package.
Download Test Environment Setup Document
Test Execution: In this stage of test life cycle test cases are executed and test result are updated as Pass/Fail/Blocked/Not Applicable based on testing outcome. Any deviation of the actual result from the execpted result is considered as defect or bug. If any defect is found a bug will be raised and assigned to the developer.
Download Test Execution Document
Download Test Execution Result (Sample)
Bug Report: All the bugs raised due to difference in actual result from the expected result will be reported and tracked in any bug tracking/bug reporting tool.
Download Bug Report Document (Sample)
Test Signoff / Test Closure / Test Summary Report: This document provides overall summary of testing such as test metrics such as test execution matrix(Number of test cases planned/executed/Failed/Blocked/Not Applicable), Bug matrix(Bugs by severity, Bugs by module etc).
Download Test Signoff / Test Closure / Test Summary Report Document
User Interface Testing Checklist (UI checklist): We prepare UI testing checklist based on the user interface to ensure that all areas are covered and to avoid missing any area of UI testing.
Requirements Traceability Marix (RTM) : It is a document that maps requirement with the test cases. This to ensure that no requirement is missedout during testing and it helps in easy tracking to understand which test scenario/test case is prepared for which requirement.
No comments:
Post a Comment