Introduction for Metro Rail SCMS version 3.0 , it


1.1 Purpose

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!

order now


This document is a test plan for
Metro Rail SCMS version 3.0 , it has been implemented and produced by the
testing IT department. Firstly, it describes the testing strategy and takes an
innovative approach so that the testing team can verify this, and to ensure
weather it will meet the company standards and IT regulations before its


The test plan will further describe
the testing approach and the framework that needs to drive the testing of the SCM


SCMS online system, is an essential
tool that will provide employees of the company that would enable them to view
relevant information, particularly their personal information as well as
updating personal information with an internet enabled PC without having to
involve the HR department.



1.2 Objectives


User friendly

Meets the software user specification

Support business function



2. Testing Scope

The modules/requirements in the scope of testing for the SCMS System
Testing  will be as follows:



Test Objective


The objective of the test will be to
verify that the functionality of SCMS version 3.0 will work according to the

Thus the test will execute and verify
the test scripts, identify and fix all high as well as medium severity defects
per the entrance criteria. It will also prioritize lower severity defects for
future fixing via CR.


The final product of the test will

A production ready software

A set of stable test scripts that can
be reused for functional and test execution.



3. Overall
Strategy and Approach

3.1 Testing

SCMS version 3.0 System Testing will
include testing of all functionalities that are in scope System testing
activities will include the testing of functionalities, work flows,
functionality access, testing of internal & external interfaces etc.


Testing will be carried out once the build will be ready for

Performance testing will not be considered for this

The test team will be provided with access to the test
environment via VPN connectivity

Test team will manage the testing effort with close coordination
with project PM/ business analyst

Business analyst will review as well as sign off test cases
prepared by test team prior to the test execution.

Project team will have the knowledge and experience necessary
or will have the adequate training in the system. The project as well as the
testing processes.





3.2 System
Testing Entrance Criteria

In order to start system testing,
certain requirement must be met for testing readiness. The readiness can be
classified into:

3.3 Testing Types


3.3.1 Usability Testing

User interface attributes, cosmetic
presentation and content will be tested for accuracy and general usability. The
goal of Usability Testing is to ensure that the User Interface is comfortable
to use and provides the user with consistent and appropriate access and
navigation through the functions of the application (e.g., access keys,
consistent tab order, readable fonts etc.)

3.3.2 Functional


During functional testing, the
testing team will use the preloaded data which will be available on the system
at the time of execution.

The test team perform functional
testing on SCMS Version 3.0. The test will be to ensure that each of the
element of the component meets the functional requirement of the business will
be outlined


According to the business Functional

Business Rules

And other functional documents that
will be produced during the course of the project.


Test Principles

Testing will be focused on meeting the business objectives
cost efficiency as well as quality.

Consistent procedures will be followed for all teams
supporting testing activities

Testing process will be well defined, yet flexible with the
ability to change as needed

Test environment and data will emulate a production
environment as much as possible.

Testing will be divided into distinct phases, so that each
with clearly define the objective and goals.

Testing phase will be well defined, yet it will be flexible
with the ability to change as needed.


3.4 Test Data

Test data
requirements are drawn up based on the functional requirements that are due for
testing. The testing team will identify test cases that can be grouped into
test scenarios and detail the data required to complete the testing activities.

Execution Plan

Execution Plan


The execution plan
will detail the test cases to be executed. The Execution plan will be put
together to ensure that all the requirements are covered. The execution plan
will be designed to accommodate some changes if necessary, if testing is
incomplete on any day. All the test cases of the projects under test in this
release are arranged in a logical order depending upon their inter dependency.









The System Testing
Environment that will be used for System Testing.


Once all test case
will be approved the test environment will be ready for testing, the tester
thus will start a explanatory test of the application in order to ensure so
that the application will be stable for testing.

Daily Test execution status
as well as Defect status will be reported to all stakeholders.

 Testing team will participate in defect triage
meetings in order to ensure all test cases

are executed with either
pass/fail category.

If there are any defects that
are not part of steps but could be outside the test steps,

such defects need to be captured
in HP ALM and map it against the test case level or at

the specific step that issue was
encountered after confirming with Test Lead.


6. Test

The system testing
will be scheduled for 8 weeks this will start from 23 february to 23 April. Moreover
the test team will complete the execution of all the test during the first 2

The run dates for
defect retesting period may be changed according to the need to retest and
close the defects. The defects retesting will reduce the number of open defects
that need to be carried to UAT.

Test Management Tool

The HP application
lifecycle management will be the tool that will be used for the test
management. All the testing artifacts such as test cases, test results will be
updated on the HP application lifecycle management (ALM) tool.

During the test design phase, all test case
will be written directly into HP ALM. Any changes to the test case will be
directly updated in the HP ALM.

During the test design phase, all the test
that will be carried will be written directly into the HP ALM. Any change to
the test case will be directly updated on the HP ALM.

The tester will understand each requirement
and prepare corresponding test case to ensure all requirements are covered.

Test Risk and
Mitigation Factors






Testing schedule is
tight. If the start
of the testing is delayed due to
design tasks, the test cannot be
extended beyond the UAT
scheduled start date.



The testing team can control the
preparation tasks (in
and the early communication
with involved parties.
· Some buffer has been added to
the schedule for contingencies,
although not as much as best
practices advise.

Not enough resources, resources on
boarding too late (process takes
around 15 days.



Holidays and vacation have been
estimated and built into the
schedule; deviations from the
estimation could derive in delays in
the testing.

Defects are found at a late stage of
the cycle or at a late cycle; defects
discovered late are most likely be
due to unclear specifications and
are time consuming to



Defect management plan is in place
to ensure prompt communication
and fixing of issues.

















Production like data required
and be available in the system prior to start of Functional Testing

? In each testing phase,
Cycle 3 will be initiated if the defect rate is high in Cycle 2.