Red Bus Test Plan

RedBusSystem Test Plan Version 1.0 Prepared By Gopinath T ....................................................................................................................................................................................................................0 Test Data Requirements ........................................ 4 3........................5 Communication plan ...................................................................................................................................................................... 3 3.......0 Project Overview .............................................................1 Software and Hardware .................................................................... 4 3.................................................. 4 3................1 Priority and Severity Guidelines ...................................................8 Defect Tracking .0 Test Strategy .................................................3 Suspension and Resumption Criteria ..................7 5....................................................................................... 3 3.......................................................2 Out-Scope................................................................................................................................................................................................................. 4 3................3 1........... 6 3.2 Remark Status .....................4 Exit Criteria (When to stop testing) .............................................................................................................8 ........................................................3 2..................................... 7 5.....................................................................7 4............................................................................................................................8 7.6 Status Reporting......................................................2 Entry criteria (When to start testing) ......................8....................................................................0 Test Environment ............0 Approvals ................................................................................3 3..1 Testing Types .7 Test Execution ............. 4 3................................................... 6 4......................................................................................................................................................... 6 3......................................................................................................1 In-Scope ............................................0 Scope ............3 2........... 7 6................................................. 5 3.....................................................8...........................................................................................................................................................................................................1 Test Deliverables ...................................Table of Contents RED BUS .........................................................................................................................................................................................0 Staffing plan .................. 3 2................... 0 Scope 2. A unique characteristic of RedBus system that allows the customers to book tickets with highly interactive features.0 Project Overview RED BUS Bus ticket booking during the offline era posed various difficulties to the customers as well as the bus operators. E-Bus Ticket booking system enables those bus service organizations to cater their services online and get benefit out of it. It also increased the franchising cost for the bus operators. Offline ticket booking reduced the scope of customers to choose different options based on their travel criterion. This system will also allows the bus service organizations to monitor their booked tickets information online which reduces the human mistakes in off line bus ticket booking process. increases accuracy and enhance the flexibility of information processing. the bus operators were also finding it difficult to monitor their bus seat filling information.2 Out-Scope  Hotels 3. RedBus ticketing system facilitates the customers to book their tickets of their desired bus services.1 In-Scope  Home  Print/Sms ticket  Cancel/Refund ticket  Buses  Sign in/Login 2. Now RedBus has enhanced new feature “Hotels” that is used to reservation of hotels thought-out the country based on facilities availability . The RedBus search engine enables customer to choose one of many buses belongs to different bus services based on their travel criterion.1 Testing Types  Smoke Testing  Regression Testing    Retesting Testing Sanity Testing Functional Testing . 2. Many small and medium bus service organizations do not have their own online bus ticket booking system.0 Test Strategy 3. At the same time.1. com 9848662545 Pavani Manager 3.2 Entry criteria (When to start testing) 1. Compatibility Testing  Cross browser Testing   Adhoc Testing Security Testing 3. All Customer Requirements should be baseline.6 Status Reporting Daily.com 855332648 2 Lakshmi Test Lead Pavani.5 Communication plan # Resource Name Responsible Email Contact No 1 Kesava Project Kesava. 3. Weekly. 3. 100% Unit testing and Integration Testing should be successful. Monthly Test Status Reporting Model . 2. All Testcases should be Reviewed and Baselined.4 Exit Criteria (When to stop testing) 1. When all Test cases executed successfully and passed.b@Virtuelltech@. 2.com 9030056631 3 Kavitha Test Lead Kavitha.3 Suspension and Resumption Criteria Suspension Criteria Resumption Criteria When Show Stopper Defects Found If patch is releases against build Rejection When there is a Change Request from the Once CR is implemented client 3. When all P0 and P1 defects are resolved and closed.t@Virtuelltech. 3.rethuri@Virtuelltech. 7 Test Execution Test Execution Flow Building the system Smoke Testing UI Testing Functionality Testing Performing Testing Regression Testing Gate B Gate A Quality Gates Quality Gate Gate A Gate C QA Delivery to RedBus. Smoke/Acceptance Test – The smoke test is designed to ensure that each built component is in a state where QA testing on the RedBus Insight application can be carried out Gate C effectively Stability of the application – To ensure that the functional testing results does not have any high or critical defects prior to begin the performance testing.3. .in Gate D Description Build Verification Test – This is to ensure that the QA Release contains all the necessary source files to build the Red Bus components Gate B and application. 8.2 Remark Status Following are the different status of Defects in Bug tracking Tool Status Description NEW A new fault identified OPEN NEW defect has been accepted into the defect tracking system FIXED Defect is resolved CLOSED Re-Tested and defect is resolved in modified build. Priority is decided by Project Manager or an individual or a group appointed by him/her. Severity is decided by QA Manager or an individual or a group appointed by him/her. Severity Classification     Very High High Medium Low Priority guidelines The Priority Scale indicates the Urgency to fix a fault.8 Defect Tracking 3. 3.Gate D Customer Release Criteria – This is defined based on the RedBus management acceptance criteria.8. Priority Classification     Very High / P0 High /P1 Medium /P2 Low /P3 3. .1 Priority and Severity Guidelines Severity Guidelines The Severity indicates the impact of the bug. 1 Software and Hardware Computer System Software Requirements Application/Web Server  X64 (or Equivalent ) with  Windows 7 4GB RAM Hardware Requirements  Intel i3 Processor  500 GB HDD  4GB RAM 5. Test Data created by QA Team will be sufficient to execute all Test case scenarios 5. QA Team is responsible for creating test data in the system.1 Test Deliverables  Test plan . An Invalid Defect HOLD Defect is not clear DEFERRED Defect is postponed or considered for enhancements DUPLICATE Defect is already posted 4.0 Test Data Requirements Test data needed to test the RedBus Product will be identified and created by Virtuell Technologies QA Team. Works as designed.in 4.0 Test Environment The test environment outlined in this section is necessary for successful execution of test cases OS Windows 7 Web Server Apace Tomcat Database Application RedBus.RE-OPEN Re-Tested and again same defect is present in modified build REJECTED Not a defect. 0 Approvals 2 No. Test Scenarios  Defect Reports   Test cases Test Summary Reports 6. Of Person 11 Lakshmi Pavani (Project Manager) Responsibility Planning & Controlling QA activities Executing Activities planned QA .0 Staffing plan Test Lead Name Test Team Members 7.