Vous êtes sur la page 1sur 8

RedBus

System Test Plan


Version 1.0

Prepared By

Gopinath T

Table of Contents

RED BUS ..........................................................................................................................................3


1.0 Project Overview ..........................................................................................................................3
2.0 Scope ...........................................................................................................................................3
2.1 In-Scope .............................................................................................................................................. 3
2.2 Out-Scope............................................................................................................................................ 3

3.0 Test Strategy ................................................................................................................................3


3.1 Testing Types ...................................................................................................................................... 3

3.2 Entry criteria (When to start testing) .................................................................................................. 4

3.3 Suspension and Resumption Criteria .................................................................................................. 4

3.4 Exit Criteria (When to stop testing) .................................................................................................... 4


3.5 Communication plan ........................................................................................................................... 4
3.6 Status Reporting.................................................................................................................................. 4

3.7 Test Execution ..................................................................................................................................... 5


3.8 Defect Tracking ................................................................................................................................... 6
3.8.1 Priority and Severity Guidelines ................................................................................................... 6
3.8.2 Remark Status .............................................................................................................................. 6

4.0 Test Environment .........................................................................................................................7

4.1 Software and Hardware ...................................................................................................................... 7

5.0 Test Data Requirements ...............................................................................................................7

5.1 Test Deliverables ................................................................................................................................. 7

6.0 Staffing plan .................................................................................................................................8

7.0 Approvals .....................................................................................................................................8

1.0 Project Overview

RED BUS

Bus ticket booking during the offline era posed various difficulties to the customers as

well as the bus operators. Offline ticket booking reduced the scope of customers to choose
different options based on their travel criterion. It also increased the franchising cost for the bus

operators. At the same time, the bus operators were also finding it difficult to monitor their bus
seat filling information. Many small and medium bus service organizations do not have their

own online bus ticket booking system. E-Bus Ticket booking system enables those bus service
organizations to cater their services online and get benefit out of it. RedBus ticketing system

facilitates the customers to book their tickets of their desired bus services. The RedBus search

engine enables customer to choose one of many buses belongs to different bus services based on
their travel criterion. A unique characteristic of RedBus system that allows the customers to book

tickets with highly interactive features. 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. Now RedBus has enhanced new feature Hotels that is used to reservation of hotels
thought-out the country based on facilities availability .

2.0 Scope

2.1 In-Scope
Home
Print/Sms ticket
Cancel/Refund ticket
Buses
Sign in/Login
2.2 Out-Scope
Hotels

3.0 Test Strategy


3.1 Testing Types

Smoke Testing

Regression Testing

Retesting Testing
Sanity Testing

Functional Testing

Compatibility Testing

Cross browser Testing

Adhoc Testing

Security Testing

3.2 Entry criteria (When to start testing)


1. 100% Unit testing and Integration Testing should be successful.
2. All Customer Requirements should be baseline.
3. All Testcases should be Reviewed and Baselined.
3.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.4 Exit Criteria (When to stop testing)


1. When all Test cases executed successfully and passed.
2. When all P0 and P1 defects are resolved and closed.
3.5 Communication plan
#

Resource
Name

Responsible

Email

Contact No

Kesava

Project

Kesava.t@Virtuelltech.com

855332648

Lakshmi

Test Lead

Pavani.rethuri@Virtuelltech.com

9030056631

Kavitha

Test Lead

Kavitha.b@Virtuelltech@.com

9848662545

Pavani

Manager

3.6 Status Reporting


Daily, Weekly, Monthly Test Status Reporting Model

3.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.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.

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.

Gate D

Customer Release Criteria This is defined

based on the RedBus management acceptance


criteria.

3.8 Defect Tracking

3.8.1 Priority and Severity Guidelines


Severity Guidelines
The Severity indicates the impact of the bug. 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. Priority is decided by Project Manager or
an individual or a group appointed by him/her.
Priority Classification

Very High / P0
High /P1
Medium /P2
Low /P3

3.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.

RE-OPEN

Re-Tested and again same defect is present in modified build

REJECTED

Not a defect. Works as designed. An Invalid Defect

HOLD

Defect is not clear

DEFERRED

Defect is postponed or considered for enhancements

DUPLICATE

Defect is already posted

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.in

4.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.0 Test Data Requirements

Test data needed to test the RedBus Product will be identified and created by Virtuell
Technologies QA Team. QA Team is responsible for creating test data in the system. Test Data
created by QA Team will be sufficient to execute all Test case scenarios
5.1 Test Deliverables

Test plan

Test Scenarios

Defect Reports

Test cases

Test Summary Reports

6.0 Staffing plan

Test Lead

Name

Test Team Members

7.0 Approvals

No. Of Person

11

Lakshmi Pavani (Project Manager)

Responsibility

Planning & Controlling QA


activities

Executing
Activities

planned

QA