2014

Test Plan
BSEF10M001 BSEF10M017 BSEF10M019 BSEF10M024 BSEF10M042 BSEF10M057

Document Overview
Title Project Client Doc # Author Hafiz Mujadid Khalid Test Plan Product Information Management System Version Status Type Doc Date Last Save 1.0 Draft Internal Jan 17, 2014 Jan 17, 2014

Description: This document describes the Test Plan for PIMS

Revision History Ver # Rev Date Author Distr Date Brief Description

Approved By Name Role Version

TABLE OF CONTENTS 1. Introduction ................................................................................................. Error! Bookmark not defined. 1.1 Objective ...................................................................................................................................... 3 1.3 Intended Audience ....................................................................................................................... 4 2. Scope............................................................................................................ Error! Bookmark not defined. 3. Functional Testing ...................................................................................... Error! Bookmark not defined. 3.1 Test Designing ............................................................................................................................. 5 3.2 Testing ......................................................................................................................................... 5 4. User Interface Testing ................................................................................ Error! Bookmark not defined. 4.1 Test Designing ............................................................................................................................. 5 4.2 Testing ......................................................................................................................................... 5 5. Testing Types .............................................................................................. Error! Bookmark not defined. 5.1 Acceptance Testing ..................................................................................................................... 6 5.2 Functional Testing ....................................................................................................................... 6 5.3 User Interface Testing ................................................................................................................. 7 5.4 Regression Testing ...................................................................................................................... 7 6. Resources ................................................................................................................................................ 7 6.1 QA Team Structure ...................................................................................................................... 7 6.2 Test Platform ............................................................................................................................... 8 6.3 Testing Tools ............................................................................................................................... 8 7. Test Management and Procedures ........................................................... Error! Bookmark not defined. 7.1 Processes .................................................................................................................................... 8 7.2 Suspension and Resumption Criteria .......................................................................................... 9 7.3 Severity Levels and priorities ....................................................................................................... 9 7.4 Exit Criteria ................................................................................................................................ 10 8. Testing Management .................................................................................. Error! Bookmark not defined. 8.1 Testing Deliverables .................................................................................................................. 10 8.2 Testing Sequence ...................................................................................................................... 11

1.

Introduction:

This document describes the Test Plan for Product Information Management System. It is intended that the QA Team will use this document to execute the system-testing phase. This Test Plan document includes a discussion on the objective and assumptions of the testing activity as well as the methodology and approach.

1.1 Objective
The objective of this test plan is to plan, organize and manage the activities/tasks that are required for the testing of Product Information Management System. This test plan is formed: To define the test scope, strategy and methodology to be used for the test To define the sources of information used to prepare the plan To identify the activities required to prepare test cases and conduct testing To identify responsibilities for the tasks included in the plan To define the test tools and the environment needed to conduct the test To identify the major testing milestones

1.2

High level functionalities:

Following known high level functionalities are:

Product Information Management by Vendors o Product basic information o Thumbnails o Primary Image o Brief description text o Product Parameters o Inventory Availability o Size/ Color Variations o Alternative Products o Products Accessories Centralized Master Product Information o Outbound Integrations o Inbound Integration o Product Workflows o Product Search o Promotion Management Vendor Product Announcements Vendor Product Advertising & Promotions Vendor Accounts Information o Vendor(s) to be able to manage their profile on their own

1.3 Intended Audience

Engagement Manager (EM) Project Manager (PM) Development Team Lead (Dev TL) Onsite Business Analyst (BA) Quality Assurance Engineer (TE)

2.

Scope:

Scope of testing may include the following as per the need of deliverable/sprint: o o o o o o o o o o o o o o o o o o o o Functional areas of the application to be tested including: Vendor Edit Organization Creation/Edit New Product Announcement User Creation/Edit User Roles Login Home Product Search Product Edit Attributes Edit Manage Variations/Accessories Alternate Products Content Pool Manage Image/Doc Contents Image/Doc Association Transfer Vendor Product Bulk Edit Bulk Uploads Price Increase & Effective Date Product Bulk Active/Inactive User Interface Testing through-out the application Areas of Regression Testing

Areas of Integration Testing System Testing

3.

Functional Testing:
3.1 Test Designing
For Functional Testing, will identify and write test scenarios and test cases based on the templates written and provided by QA team which have been already been acknowledged

Test scenarios and test cases will be documented in either MS Excel or MS Word format, depending upon their ease.

3.2 Testing
For detailed testing, QA team will first execute test scenarios and test cases .The same processes of reporting and fixation of defects will be followed accordingly. Pass/Fail results will be published afterwards. While executing these scenarios/cases, within each individual screen/page of the application, complex scenarios will be executed first.

4.

User Interface Testing: 4.1 Test Designing

For User Interface Testing, QA team will verify a check-list of standards which are already documented in compliance to software Specified Standards.

4.2 Testing
For each individual screen/page of the application, QA team will verify every single part of the GUI Checklist in order to achieve quality through-out the applications user interfaces. In case any part of the screen/page doesnt meet the standards described in the checklist, QA will report defects and will get the fixes accordingly.

5.

Testing Types:
5.1 Acceptance Testing

Test Objective: Technique:

To execute and verify basic functionality/flow of the application. Execution of selected Test Cases with the plan to identify all of the crashing issues which stop further testing. All of the basic functionalities/flows are verified against

required data. Completion Criteria: All selected planned test cases have been executed. Special Considerations: Environment N/A Product Information Management System All identified defects have been reported.

5.2 Functional Testing

Test Objective: To ensure that each element of the application meets the functional requirements. All functionalities, business rules, user roles etc. mentioned in design document should completely be followed and their implementation should be verified as well. Technique: All of the Test case will be executed, to verify the following: Each and every functionality/flow is verified against required

data. Completion Criteria: Special Considerations: Environment N/A Product Information Management System All identified defects are reported and their fixes are verified. The expected results are displayed.

5.3 User Interface Testing

Test Objective: To ensure that GUIs including text, colour, alignment, navigation etc. are totally according to the provided Requirements. Technique: All of the GUIs and their navigation will be tested based on the

GUI Checklist Completion Criteria: Special Considerations: Environment N/A Product Information Management System The GUIs are verified according to GUI checklist. All identified defects are reported and their fixes are verified. The expected results are displayed.

5.4 Regression Testing

Test Objective: To ensure the applied changes do not adversely affected previously tested functionality. Since testing is done multiple times due to new releases/builds, there are chances that some part of the application may get affected. Technique: Those test cases will be executed that cover the larger area of application which is unchanged but can be affected by the changed area. Completion Criteria: Special Considerations: Environment N/A Product Information Management System All identified ripples are reported and their fixes are verified. The expected results are displayed.

6.

Resources: 6.1 QA Team:

Role Project Manager QA Engineer

Resource Assigned Hafiz Mujadid Khalid Mudassir Hussain

6.2 Test Platform

Testing will be performed on MS Windows based operating systems.

6.3

Testing Tools

Following testing tools will be used during testing: Test Management Tool o Mercury Quality Center 9.0 (Offshore) o Excel/ Word (Onsite) Web Browsers o Chrome o Firefox o Internet Explorer (10+) Screen Capturing Tools o SnagIt o Snipping Tool

7 Test Management And Procedures;

This section describes the methodology and approach used to test Product Information Management System

7.1 Processes
Following process is applied Process Definition Verification & Validation

7.2 Suspension and Resumption Criteria

Any test failure that prevents testing of any area will cause the suspension of general testing. However, if any area can be tested effectively in spite of the failure, tests will continue on those area to the extent possible.

A patch or, if appropriates, a new release that corrects the failure must be provided before the test process can be resumed. Before the test cycle is resumed, regression testing will be

performed to verify that the patch or new release does not adversely affect existing functionality.

7.3 Severity Levels and priorities

Currently available severity levels are as follows: Critical Significant Cosmetic Suggestion

Descriptions of Severity levels are as follows:

Critical
The severity said to be critical if it encounters following reasons: Independent Functionality (Missing, Completely not working, Major Portion not working) Showstoppers (may not be an independent functionality but effects testability)

Significant
The severity said to be significant if it encounters following reasons: Incorrect functionality, data population, missing minor functionality, consistency issues (flow or functionality related), etc. Crashes that dont affect the testability or are not showstoppers These are not cosmetic defects

Cosmetic
The severity said to be cosmetic if it encounters following reasons: Controls positioning, spelling mistakes, grammatical mistakes Non User friendly messages, inconsistent messages Consistency of layout and format on all the GUIs Tabbing sequence etc.

Suggestions

The suggestion describes the ability that causes enhancement in the currently available functionality. It has to fulfill the following criteria Suggestion should be purely enhancement Major functional change that is a contradiction to the baseline document is not a suggestion Suggestion is something that can improve application readability Inconsistency in application is not suggestion It cant be reported without the consent of QA Team Lead.. Anything that is referring to some standard (GUI checklist, style guide) that is being used in the project cannot be a suggestion

Priories of defects will be in following sequence. Urgent Very high High Medium Low

7.4 Exit Criteria

The exit criteria for the test phase are: All planned test cycles have been executed

No identified bugs are open. 8 Test Management:

8.1 Testing Deliverables
Deliverable Name Test Plan Test Strategy Application Acceptance Criteria Test Specifications (Test Scenarios, Test Cases) External Test Planning External/Internal Internal Internal External Baseline Phase Analysis, Test Planning Test Planning Test Planning

Defect Reports Testing Status Reports Test Execution Records Tested Application Code Shipment Notes

External External External External External

Testing Testing Testing Shipment Assurance Shipment Assurance

8.2 Testing Sequence

Complex scenarios will be executed first within individual report. Following sequence will be followed for Test Cases Prioritization. At first release will be evaluated against Application Acceptance Criteria to ensure the Testability of the release i.e. Acceptance Testing. After the Acceptance Testing, functionality of higher weight-age will be Target First. Weight-age of the functionalities are calculated on the following basis o o o Effort involved in Total Testing of Particular Testing Complexity of each functionality GUI Standards