Professional Documents
Culture Documents
QSmart
SIGNATURE
15/6/2001
DATE
Table Of Contents
OVERVIEW........................................................................................................................3
Purpose.................................................................................................................................3
Scope.....................................................................................................................................3
TEST PRE-REQUISITES.................................................................................................4
REFERENCES.................................................................................................................26
ANNEXURES...................................................................................................................28
CHANGE LOG.................................................................................................................29
WRAP-UP.........................................................................................................................30
REFERENCES.................................................................................................................31
ANNEXURES...................................................................................................................33
CHANGE LOG.................................................................................................................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
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:
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.
2 Project Details
3 Estimation
Worksheet
3.2 Click the browse This will copy the file to the
button and select server.
the file which u
want to attach, and
press submit.
8 Project
Retrospective
9 Project Audit
Planning
9.2 Enter all the details It will trigger mail to Audit Area
& submit the form. Rep. & CC to QR based on
user Confirmation status.(if
yes mail will be sent otherwise
no mail wil be sent)
10 Fact Recording
Sheet
11 Close-Follow up NC
12 View NC
13 Support Services
14 Fact Recording
Sheet
15 Close/Follow-up
NC
16 View NC
17 QSM Deviation-
18 QSM Feedback -
19 Internal Tool
Feedback
20 Customer
Complaints
Module: Reports
21 Project Based
22 Open NC Status
23 NC Status –
Consolidated
24 NC Closure
Duration.
25 SQA Monitoring
26 SnapShot Report
Module: Administration
27 Project Information
29 Support Service
30 Process
31 Roles
3 Fact Recording
2.4 Sheet
3 Close-Follow up NC
2.7
3 View NC
2.1
0
3 View Observations
2.1
4
33 Project
Submodules
Wrap-up
This sub-section should specify the operations to be performed after the
procedure has been executed. Some of these could be:
References
This section should provide references to other project documentation, which can
provide more information on the item being tested.
NA Not Applicable
Annexures
This section may contain information specific to the project such as:
Change Log
Wrap-up
This sub-section should specify the operations to be performed after the
procedure has been executed. Some of these could be:
References
This section should provide references to other project documentation, which can
provide more information on the item being tested.
Annexures
This section may contain information specific to the project such as:
Change Log