Anda di halaman 1dari 5

System Test Execution Guidelines

Modification History
Version

Date

Name

Reviewer

Description

No.

Table of Contents

Guidelines - While execution of test cases in TESTLAB...4


Guidelines - While raising Defects in Quality Center ...........................6
Guidelines - While Updating / Closing Defect in Quality Center .8
Guidelines - Attaching documents in Quality Center .9

Guidelines While execution of testcases in TEST LAB.

1. Before starting the execution for any release, Release execution pre-start checklists must be
followed. Pre-start checklists helps test lead to decide whether we are in a position to start the test
execution or not. (To be followed by coordinators and test lead)
2. Every tester need to execute the allocated test cases by the coordinator on daily basis. The daily
execution status report should be updated as soon as the tester finishes execution of a single TC.
3. When a test case is being executed first time i.e.: Test case is in No Run status, tester should start
a fresh manual run of the test case . If a test case is not in No Run or Passed status then tester must
continue the previous run without deleting the previous comments.
4. TEST EXECUTION - Actual Results Comments Update
During systest execution, while executing a Test Case , the Actual Results Section in QC should
be updated with full information. Previous comments which were written while the error was
raised should NOT be deleted. In actual results section for each & every test step, the tester
must put his/her QC id as well as Date along with test results
After Raising an Error:
The Actual Results section for a FAILED step should be updated with the following information:
a) Today's Date
b) Tester's RACFID:
c) Error No.:
d) Description of the Actual scenario
After Closing the Error:
The Actual Results section should be updated with following information, after retesting:
a) Today's Date
b) Tester's RACFID
c) Error No: with comments saying 'Error Closed'
d) If the step is PASSED then update it with comments 'As Expected'
5. Tester should discuss with the test prep/exec lead and also refer to CRs/FDDs/Supporting
documents before making a test step as NA. Then proper justification/reason must be updated in
the actual results column where the step is being converted in to NA.
6. For all Failed or Blocked test cases , Blocking Defect column in Quality Center must be filled with
latest QC Defect no . As soon as that QC defect gets fixed, QC Defect number must be removed from
defect ID column and should be put into Defect ID in Progress field. At that stage Defect ID field
must be blank as that QC Defect is resolved.
7. All test cases must be executed till the step where an error occurred with proper information in
actual result field. Fast run of test cases must not be done.
8. There must be only one test run for any test case. More than one instance is not acceptable.
9. Any discrepancy in any of test step from actual result must be clearly updated in description section
and must be saved after end run. So that it will be reflected in test plan.

Anda mungkin juga menyukai