TEST PROCESS

Work Products Creation (Deliverables)

During the Testing phases, various deliverables will be provided as outcome. These are listed as follows

· Gap Analysis Report

· Requirement Traceability Matrix

· Test Strategy

· Estimation Report

· HLP/MLP for the release

· High Level Test Scenarios

· Selenium Script

· Defect Status Report

· Test Completion Report
4.1.1 Gap Analysis Report

After getting the Project Requirements, we have logged our various queries in Requirement Query Log and discussed these in the client meetings. The Gaps in understandings were logged into this document.
4.1.2 Requirements Traceability Matrix (RTM)

After the requirements have been frozen by the client and the test cases are signed off by the user. The QA Team would form the Requirement Traceability Matrix and get it signed off from the client confirming that all the requirements have been covered
4.1.3 HLP/MLP

During this iteration for quality assurance, the team has been working in synchronization with the High-level plan and Mid-Level Plan
4.1.4 Estimation Report

Various Time and Effort estimations were included in the Estimation Report. These estimations are mapped with the HLP also.
4.1.5 Defect Status Report

Depending upon the outcome of each and every test case executed defects would be logged and the number of defects that are found would be logged and reported back to the stakeholders. All the defects encountered during test execution are logged in Jira and a Defect Status Report is generated.
4.1.6 High Level Test Scenarios (HLTS)

The High Level Test Scenarios have been created by test leads and the QA Manager.
4.1.7 Test Cases

All the test cases would be created by the Test Analyst and would be validated by the Test Lead to make sure that the test cases map back to the requirements the user had defined.
4.1.8 Test Scripts

All the test cases once manually tested will be automated into scripts using Selenium
4.1.9 Test Completion Report

After execution of all tests, it is recorded in the Test Completion Report which explains the number of test executed or gated or passed or failed and the overall test coverage.

4.2 Work Products Review Process
· Test Deliverables Review

Each of the deliverables would be reviewed by the test lead and the QA Manager before being delivered to the client.
· Maintenance of Test Cases/Scripts

The various test cases and scripts would be regularly updated and versioned by the QA Team in order to make things coordinate much better. If in case the test cases/scripts have been changed by the user depending upon change in defect or requirements, due to versioning of scripts we would be able to map defects to the version of case/script that caused it.

4.3 TEST MANAGEMENT

4.3.1 Test Environments
· System Test Environment

QA team will create both manual and automated test scripts based on the requirements mentioned in the wireframes and FSD’s. These scripts will be executed on the local QA environment which will consist of both authoring as well as publishing instances. This environment will be based locally within Sapient environment.
· System Integration Test Environment

Once all test scripts have been successfully executed on the system test environment and there are no open P1’s and P2’s on the test environment. Along with the system test scripts, QA team will create and execute End 2 End test scripts on the SIT environment. Please note that the SIT environment will be a scaled down version of the production environment which will consist of both authoring as well as publishing instances. This environment will be based locally within stakeholder environment.
· UAT Environment

This environment will also be used as the Production environment wherein UAT test scripts (created by Stakeholder) will be executed and finally a Go/No Go sign-off decision will be provided. Post UAT sign-off, application will be deployed on the Production environment (during the cutover phase) and application sanity will be tested on the production environment. Please note that all System Test scripts will not be executed on the production environment. This environment will also consist of both authoring as well as publishing instances.

4.3.2 Test Data Management
· Test Data from Production

The test Data would be provided to us by the client. The data should have been validated and be data from the production environment
· Test Data Creation

The dummy data provided to us would be used to create new data. We would use the front end applications of the user to create that data
· Test Data Maintenance



The data would be versioned and saved. This would help preserve the original data as well as show the various transitions in the data that might have happened as the data moved through the application