Qsmart Testing Procedure-V1

Controlled Copy

Cognizant Technology Solutions

QSmart

TEST PROCEDURE FOR NEW TECHNOLOGY PROJECTS

Ver No. 1.2

PREPARED BY REVIEWED BY APPROVED BY

NAMESivaraman G Sambit Mishra Emani Sarathy

ROLETeam Member Project Leader Project Manager

SIGNATURE

DATE15/6/2001

Approved and Issued By: MQA Form No: QTNTEST.DOC/7.0 Date: April 24, 2000

Controlled Copy Test Procedure - Template

Table Of Contents

OVERVIEW................................................................................................................. 0

Purpose.......................................................................................................................... 0Scope............................................................................................................................. 0

TEST PRE-REQUISITES............................................................................................0

DETAILS OF TEST CASES.......................................................................................0

Features Tested.............................................................................................................. 0Execution....................................................................................................................... 0

WRAP-UP.................................................................................................................... 0

REFERENCES............................................................................................................. 0

DEFINITIONS AND ACRONYMS.............................................................................0

ANNEXURES............................................................................................................... 0

CHANGE LOG............................................................................................................0

WRAP-UP.................................................................................................................... 0

REFERENCES............................................................................................................. 0

DEFINITIONS AND ACRONYMS.............................................................................0

ANNEXURES............................................................................................................... 0

CHANGE LOG............................................................................................................0

Proj. ID SCI. ID S. No. Doc. Version Form No: QTNTTEST.DOC/7.0NTTEST w. e. f. April 24, 2000

Page 2 of 34


Overview

This sub-section should specify the following:

Purpose

This procedure tells about the different test cases to be executed for the successful implementation of QSmart

Scope

All the user Interfaces

Proj. ID SCI. ID S. No. Doc. Version Form No: QTNTTEST/7.0NTTEST w. e. f. April 24, 2000

Page 3 of 34


Test Pre-Requisites

This sub-section should state all the key events occurred before execution of the test procedure. Some examples of such events are:

Mobilization of all resources required to start the procedure.

Completion of all preparatory activities (for example, booting the system, loading software to be tested, invoking windows, creating and validating test data etc.).


Page 4 of 34


Details of Test Cases

Features Tested

This sub-section should state the specific features tested by the current test case. For all the features specified here, test cases will be given in the next section.

Execution

Execution details of a test case depend on the application and hence can vary widely. The application could be a batch job, or an interactive one calling for on-line inputs, or a client-server job calling for a totally different approach. Given the wide diversity of tests, it is not advisable to impose a standard. However, it is suggested that irrespective of nature of the test case, the following minimum information be recorded about the execution details of the test case:

All details about every activity to be done (what is to be done, when, how etc.)

Data and other input to be given, if any.

Behavior expected of the system.

Evaluation procedure, for interpreting the results.

Control decisions: When to start, end, suspend, resume, rerun the test; actions to be taken in case of exceptional situations.

Any other relevant aspect.

Two key activities in the stated list need special attention. One is recording or noting down the output behavior of the system. The other is saving or backing up specific portions of the test environment (inputs, intermediate outputs, screens, reports, files created etc.).

If the test designer expects the test team to record or note down the behavior observed in a particular format, then he/she should provide samples of such forms as Annexures to the test procedure, along with clear instructions on how the recording should be done. As an example, a blank form is provided in Annexure A to this document.

If portions of the test have to be backed up, then this sub-section should provide specific instructions about these aspects, along with details of the medium to be used (forms, reports, floppies, tapes etc.).

As stated earlier, if the current test case is to be broken down into sub-tests, the above information should be provided for every sub-test in the current test case.


Page 5 of 34


The information can be presented in the form of the following table with all applicable features to be tested:

Module: Project Information

Associated Programs: Workorder Details, Project Details, Estimation worksheet, PSPPH, QGBM, Project Retrospective.

ID Test Case Expected Result Remarks

1 Work order Details -

1.1 Enter Project ID to Raise Work Order/click on Raise work order link

Project Work order window will open

1.2 Enter all the details & submit the form

If Intender signed then mail will be triggered to reviewer. If not signed mail won’t be triggered & the work order won’t be submitted for review.

1.3 click on “FOR REVIEW”

work order link / click on

the mail URL

Work order details will open

1.4 Reviewer will take action

Mail will be triggered based on reviewer sign status.If “yes” mail will be triggered to approver. Else mail will be triggered to the intender

1.5 If mail comes back to intender he will again change the work order & submits it.

Mail will be triggered to reviewer again

1.6 click on “FOR Approval”

work order link / click on

the mail URL

Work order details will open

1.7 Approver will take action

If “yes” mail will be triggered to MQA Designates and TSA. Else mail will be triggered back to the intender. And this cycle will continue till it is approved.


Page 6 of 34


1.8 Click on “Approved “ link

The approved workorder will be shown in a non editable text. From there workorder can be revised.

2 Project Details

2.1 Click “Project Details” Link, Click on the project name.

The Project Repository form will open.

2.2 Enter the project detail and press save or submit button.

The details has to be entered in the backend.

2.3 Red – Initial stage(New)

Yellow – Half filled (Saved State)

Green – Holds all the Information(Submitted Sate)

NA

3 Estimation Worksheet

3.1 Click on “Attach” link.

This will open the form to Attach the Estimation Worksheet file to that project.

3.2 Click the browse button and select the file which u want to attach, and press submit.

This will copy the file to the server.

3.3 Click the “Update” link and click on the project.

Opens the form to update the Estimation worksheet attachment.

3.4 Do as in 3.2 Same as in 3.2

3.5 Click on “Estimation Worksheet” link. The default view “view” will be

This will open the Estimation Worksheet, which is attached with the Project.


Page 7 of 34


enabled. Click on the Project Name.

3.6 Click on “Delete” link.

This Projects with attachments will be listed ,if u click any project from the list a alert message will be called “ Sure you want to delete the file ?“ with the Option Ok and cancel. If clicked Ok the Estimation Worksheet Attachment will be deleted , if cancel clicked the action will be stopped.

4 SPP

Same testcases has to be followed like testcase no 3.

The Actual result will be same like the testcase no 3.

5 PSPH


The Actual result will be same like the testcase no 3.

6 PSPPH

This document will be done only for New Technology Process.


The actual result will be same like the testcase no 3.

7 QGBM



8 Project Retrospective

8.1 Click on the “Create” link, click the project on which you want to create

Open the Projects Retrospection form.


Page 8 of 34


Project Retrospective.

8.2 select the project retrospective stage.

If the retrospective exists for the selected stage it will popup the error message. If not it will create the retrospective for that stage.

8.3 Click on “View” link. Click the project and the stage of the retrospective you want to view.

It will show the retrospective form on which u can able to view and edit the retrospective details.

Module: Audit Planning & Monitoring

Associated Programs: Project Audit Planning, Fact Recording Sheet, Close/Follow-up NC, View NC, Create Project Report, View Project Report, QR Plan


9 Project Audit Planning

9.1 Click on the project for which new plan has to be created

New Window will open with scheduled start date, end date & Planned effort

9.2 Enter all the details & submit the form.

It will trigger mail to Audit Area Rep. & CC to QR based on user Confirmation status.(if yes mail will be sent otherwise no mail wil be sent)

9.3 Modify the Audit Plan-Enter all the details for Revision/ Completion

It will trigger mail to Audit Area Rep. & CC to QR based on user Confirmation status.(if yes mail will be sent otherwise no mail will be sent)

10 Fact Recording Sheet

10.1

Click on the link “Fact Recording

Fact Recording sheet will open


Page 9 of 34


Sheet”

10.2

Enter all the details & submit

It will trigger mail to Audit Area Rep. & CC to QR based on user Confirmation Status.(if yes mail will be sent otherwise no mail will be sent)

11 Close-Follow up NC

11.1

Click on any project Link pertaining to the project

Project Fact Recording sheet will appear .

11.2

Click on any of the links-

1. convert to NC

2. Convert to Observations

3. Close findings

The finding will be locked. Entry of corrective actions to be taken


Findings will be closed

12 View NC

12.1

Click on “View NC” List of Projects will appear with hyperlinks to NCs.

12.2

Click on “NC Note No”

NC closure form will open with all the details.

12.3

Fill up all the details including “NC Follow up” & Document Reference “ & click on submit button

The NC Status will be closed

Module: Support Services

Associated Programs: Support Services Details, Fact Recording Sheet, Close/Follow-up NC, View NC


13 Support Services


Page 10 of 34


13.1 Click on Support Service name.

Opens the Support service details form on which we can edit the details.

13.2 Edit the Support service detail and submit.

Updates the details in the database (back end).

14 Fact Recording Sheet

14.1 Click on the Support service name.

Opens the Fact Recording Sheet Report page.

14.2 Click “Create New” button.

Opens the Fact Recording Sheet

14.3 Enter the Data and press submit.

Mail will sent to the Audit Representative about the Facts information.

14.4 Click “Summary Mail”.

Summarized mail will be sent to the PL of that project for that Facts alone.

14.5 Select the action from the combo box.

Opens corresponding form for action.

14.6 Enter the details on the form and press submit.

Stores the data entered in the database.

15 Close/Follow-up NC

15.1 Click on the project name.

Opens the Project Non Conformance Report which will list only OPEN NC’s .

15.2 Click on the NC Note no.

Opens the NC form for follow up.

15.3 Enter the details and Click submit button.

Updates the backend with the follow up of NC data.

16 View NC

16.1 Click on the Opens the Project Non conformance report on which


Page 11 of 34


Project name we can see NC’s of all Status.

16.2 Click on the NC Note no.

Opens the NC form on which we can edit the details, depend on the NC status.

Module: Process Improvement

Associated Programs: QSM Deviation, QSM Feedback, Internal Tool Feedback, Customer Complaints


17 QSM Deviation-

17.1

Click Create under the module QSM Deviation

All the approved projects for which deviations can be created will listed. Only the Project members can created a deviation for the respective project.

17.2

Click the project for which deviation has to be created.

A window will Open which will have the generated deviation id, which will be in the format USERID/GENERATED NUMBER.

17.3

Enter all the details and submit for review.

If Intender signed then mail will be triggered to reviewer. If not signed mail won’t be triggered & the work order won’t be submitted for review.

17.4

click on “VIEW link / click

on the mail URL

All the deviation created will be displayed project wise, if click the project the deviations for the respective project will be listed with their status.

17.5

Reviewer will take action

Mail will be triggered based on reviewer sign status. If “yes” mail will be triggered to approver. Else mail will be triggered to the intender

17.6

If mail comes back to intender he will again change the

Mail will be triggered to reviewer again


Page 12 of 34


deviation & submits it.

17.7

To approve follow 1.4 /

click on the mail URL

Deviation created will be shown

17.8

Approver will take action

If “yes” mail will be triggered to Intender and Reviewer Else mail will be triggered back to the intender. And this cycle will continue till it is approved.

17.9

Approved deviation s

The approved deviation will be shown in a non-editable text.

18 QSM Feedback -

18.1

Enter Feedback for a Particular Review Item of a Stage of Process Model

Feedback will be saved with the Suggestion

18.2

Attach Feedback in a form of a file

File attached and indicating an icon for changes

18.3

Not entering the Name of

the Person who entered

Feedback

Should take Anonymous as Default

18.4

Reviewer taking action on the QSM Feedback

Review results saving and change of status according to reviewal status

18.5

Approver action on QSM Feedback

Approval results saving with reasons if not approved and change of status accordingly

19 Internal Tool Feedback

19.1

Tool Feedback for particular Tool

Accept the Feedback with Suggestion, attachment (if any)

19.2

Feedback raised not willing to give own name

Take Anonymous as default


Page 13 of 34


19.3

Reviewer entering action to be taken with details on resources required

Details to be accepted and the status of Feedback to be changed to “Waiting of Approval”

19.4

Approver decision on Feedback

Detail of Approval and reason if non Approval to be taken with status change accordingly

20 Customer Complaints

20.1

Customer Complaint raised by Project member

Saving of details with suggestion, Reported by person, and person responsible and category

20.2

Customer Complaint Action with Person Responsible

Saving of detail of action taken, preventive action to be taken and status of complaint.

Module: Reports

Associated Programs: Project Based, Open NC Status, NC Status - Consolidated, NC Closure Duration, SQA Monitoring, SnapShot Report.


21 Project Based

21.1 Click on “Location wise” link, select the location and press “Generate” button.

Shows the Projects information based on the location selection.

21.2 Click on “Statuswise” link, select the Status and press “Generate” button.

Shows the Projects information based on the Status selection.

21.3 Click on “Process Model wise” link, select the Process Model and press “Generate” button.

Shows the Projects information based on the Process Model selection.


Page 14 of 34


21.4 Click on “Typewise” link, select the Type and press “Generate” button.

Shows the Projects information based on the Type selection.

22 Open NC Status

22.1 Click on ”Projectwise”, select the Project and press “Generate Report” button.

Shows the selected project NC information with the link to NC - Form.

22.2 Click on ”Project Managerwise”, select the Project Manager and press “Generate Report” button.

Shows the selected PM’s NC – Details by Project wise with link to NC form.

22.3 Click on ”Quality Reviewer wise”, select the Quality Reviewer and press “Generate Report” button.

Shows the selected QR’s NC Details by Project wise with link to NC form.

22.4 Click on ”Location wise”, select the Location and press “Generate Report” button.

Shows the selected Location’s Project wise NC details with the link to NC form.

23 NC Status – Consolidated

23.1 Select Month, Year and Location and click generate Report.

Shows the NC’s count on raised, Closed etc., and Not Agreed NC’s with the link to the NC form.

24 NC Closure Duration.


Page 15 of 34


24.1 Click on “NC Cyclewise” link, select location and Audit cycle number then press “Generate Report” button.

Shows the Minor, Major, and overall NC’s, Average, maximum, and Minimum time of Closure duration for the selected location and Audit cycle number.

24.2 Click on “Projectwise” link, select the project and press “Generate Report” button.

Shows the Minor, Major, and overall NC’s, Average, maximum, and Minimum time of Closure duration for the selected project.

25 SQA Monitoring

25.1 Click on “Actual Vs Planned” link. Select a month and year then click “Generate report” button.

Shows the Actual Vs Planned report Statistics and link to the Activity Report, on the project name.

25.2 Click on the “Startup Audit Elapsed Days” link, enter start date and end date then click “Generate Report” button.

Shows the Project Elapsed days Statistics.

25.3 Click on “SQAG Metrics By Activity” , select month, year, location, and activity then click on “Generate Report” button.

Shows the SQAG Metrics Report with the Statistical data.

25.4 Click on “Defaulters List”, select month and year then click on “Generate Report” button.

Shows the Planned Activity related reports for the selected month and year.

26 SnapShot Report

26.1 Click on the Opens the SnapShot report as of the current date which


Page 16 of 34


“SnapShot” link. consists of Location wise ongoing project, Process Model wise, QR wise etc.,

Module: Administration

Associated Programs: Project Information, Audit, Support Service, Roles


27 Project Information

27.1

Select a parameter from the dropdown combo box.

The Corresponding Master details will be showed with the Add, Modify and Delete options, with the default selection or Add option.

27.2

Type in the data and press “>>” button.

The data will be added in that database for that specific parameter.

27.3

Click on the “Modify” link.

Opens the Modification page.

27.4

Select a the data from the list box on which u want to make modification, and edit the data in the text box and press “<<” button.

The data will be updated in the back end for that specific parameter.

27.5

Click on “Delete” link.

The Deletion page will be displayed.

27.6

Select the data u want to delete and press the “Delete” button.

The data will be updated with delete flag as 1 which specifies that the data has been deleted from further use.


Page 17 of 34


28 Audit



29 Support Service

29.1

Click on “Add” link. Opens the Support service addition form.

29.2

Select the project by click the “...” button press “>>”

Adds the project as a support service.

29.3

Rest of the things are the same as in the testcase no 1.3,1.4,1.5,1.6.

The actual result will be the same as in the testcase no 1.3,1.4,1.5,1.6 respectively.

30 Process

30.1

Follow the same procedure same as in the testcase no 27.1,27.2,27.3,27.4,27.5,27.6

The actual result will be the same as in the testcase no 27.1,27.2,27.3,27.4,27.5,27.6 respectively.

31 Roles

31.1

Click on the “Add” link.

Opens the User Addition form.

31.2

Select the name by clicking the “…” button and Select the role from the dropdown. Press submit.

Adds the user in the corresponding table depend on the selection made in the Role dropdown.

31.3

Click on “Delete” link.

Opens the user Deletion form.

31.4

Select the role from the dropdown and select the associate from the list and press “Delete”.

Marks the particular associate for deletion. So that further use of the associate for that selected role can be restricted.


Page 18 of 34


Module:Multiple QR and IQA Audit Plan

Associated Programs: Project Audit Planning, Fact Recording sheet, View Nc , View Observations


32 IQA Audits in Audit Planning

32.1

Click on the project for which new plan has to be created

New Window will open .Select the Quality Reviewer,IQA Number, & Location etc.

32.2

Enter all the details & submit the form.


32.3

Modify the Audit Plan-Enter all the details for Revision/ Completion


32.4

Fact Recording Sheet

32.5

Click on the link “Fact Recording Sheet”

Fact Recording sheet will open

32.6

Enter all the details &submit(By selecting the IQA planned audit no the IQA No and location will be displayed

It will trigger mail to Audit Area Rep. & CC to QR based on user Confirmation Status.(if yes mail will be sent otherwise no mail will be sent)


Page 19 of 34


32.7

Close-Follow up NC

32.8

Click on any project Link pertaining to the project

Project Fact Recording sheet will appear .

32.9

Click on any of the links-

4. convert to NC

5. Convert to Observations

6. Close findings



Findings will be closed

32.10

View NC

32.11

Click on “View NC” List of Projects will appear with hyperlinks to NCs.

32.12

Click on “NC Note No”

NC closure form will open with all the details such as IQA NO, Location etc.

32.13

Fill up all the details including “NC Follow up” & Document Reference “ & click on submit button

The NC Status will be closed

32.14

View Observations

32.15

Click on View Observations

List of Projects will appear with hyperlinks to View Observations

32.16

Click on “OBS Note No”

Observation form will open with all the details such as IQA NO, Location etc.

33 Project Submodules

33.1

Click on project details by clicking a

Project Details screen will open with hyperlinks to


Page 20 of 34


project create/view submodules

33.2

Click on create submodule link

Project Sub-Modules form will open.

33.3

Enter all the details such as Module name,Module start date,module end date,module leader etc and submit the form

The details will be saved in the backend,and redirected to a new screen which has the link to create another module, and view the existing module details

33.4

Click on the Audit planning link which is listed on the right side of the frame

A pop-up window will open which has the link to all the modules.

33.5

Select the particular module name and then proceed like as test case 9

The actual result will be same as test case no 9

33.6

Click the Fact recording sheet link which is listed on the right side of the frame

A pop-up window will open which has the link to all the modules

33.7

Select the particular module and then proceed like as test case 10

The actual result will be same as test case no 10

33.8

Similarly follow the test case 11 and 12 for Close/Follow up Nc and View Nc after selecting the module from the pop-up window.

The actual result will be same as test case no 11 and 12

33.9

Similarly follow the test case 32.14 for view observations after selecting the module from the pop-up window.

The actual result will be same as test case no 32.14


Page 21 of 34



Page 22 of 34



Page 23 of 34



Page 24 of 34


Wrap-up

This sub-section should specify the operations to be performed after the procedure has been executed. Some of these could be:

Exiting out the item being tested.

Backing-up important files created in course of the test.

Returning the configuration to the pre-test environment (deleting intermediate files etc.).

Other tasks to be done before the start of the next test procedure.


Page 25 of 34


References

This section should provide references to other project documentation, which can provide more information on the item being tested.


Page 26 of 34


Definitions and Acronyms

This section defines all terms, acronyms and abbreviations used in this document.

PSPPH Project Software Process and Planning handbook

QGBM Quality Goals & Project Bench-Marks

TPR Test Procedure

TLG Test Log

RSD Requirement Specification Document

NA Not Applicable


Page 27 of 34


Annexures

This section may contain information specific to the project such as:

Data specially prepared for carrying out the tests.

Tables to enter observations or data displayed.

Forms and templates that can be used for the testing.

Test scripts.


Page 28 of 34


Change Log

Old Version No.

Changes Effected

Page Number

New Version No.

Effective date

Remarks


Page 29 of 34


Wrap-up

This sub-section should specify the operations to be performed after the procedure has been executed. Some of these could be:

Exiting out the item being tested.

Backing-up important files created in course of the test.

Returning the configuration to the pre-test environment (deleting intermediate files etc.).

Other tasks to be done before the start of the next test procedure.


Page 30 of 34


References

This section should provide references to other project documentation, which can provide more information on the item being tested.


Page 31 of 34


Definitions and Acronyms

This section defines all terms, acronyms and abbreviations used in this document.


Page 32 of 34


Annexures

This section may contain information specific to the project such as:

Data specially prepared for carrying out the tests.

Tables to enter observations or data displayed.

Forms and templates that can be used for the testing.

Test scripts.


Page 33 of 34


Change Log

Old Version No.

Changes Effected

Page Number

New Version No.

Effective date

Remarks


Page 34 of 34

Documents

Qsmart Testing Procedure-V1