Test Execution Guidelines 1

Embed Size (px)

Citation preview

  • 8/9/2019 Test Execution Guidelines 1

    1/5

    System Test Execution Guidelines

    Modification History

    Version Date Name Reviewer Description

  • 8/9/2019 Test Execution Guidelines 1

    2/5

    No.

    Table of Contents

  • 8/9/2019 Test Execution Guidelines 1

    3/5

    Guidelines - While execution of test cases in TEST!"#################...$ Guidelines - While raisin% Defects in &ualit' (enter .###########..........................) Guidelines - While *pdatin% + (losin% Defect in &ualit' (enter ##############., Guidelines - !ttachin% documents in &ualit' (enter ###################.

    Guidelines While execution of testcases in TEST LAB.

  • 8/9/2019 Test Execution Guidelines 1

    4/5

    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.!"ery 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 T#.

    3.$hen a test case is being executed first time i.e.% Test case is in &'o Run status, tester should start

    a fresh manual run of the test case . )f a test case is not in 'o Run or Passed status then tester must

    continue the pre"ious run without deleting the pre"ious comments.

    4.T!*T !+!#T)' - ctual Results #omments pdate /

    During systest execution !hile executing a Test "ase the #ctual $esults Section in %" should

    &e updated !ith 'ull in'ormation. (re)ious comments !hich !ere !ritten !hile the error !as

    raised should *+T &e deleted. ,n actual results section 'or each e)ery test step the tester

    must put hisher %" id as !ell as Date along !ith test results

    #'ter $aising an Error/The ctual Results section for a 0)1!2 step should be updated with the following information%

    a Today3s 2ate

    b Tester3s R#0)2%c !rror 'o.%

    d 2escription of the ctual scenario

    #'ter "losing the Error/

    The ctual Results section should be updated with following information, after retesting%

    a Today3s 2ate

    b Tester3s R#0)2c !rror 'o% with comments saying 3Error Closed'

    d )f the step is P**!2 then update it with comments 3As Expected'

    0. Tester should discuss with the test prep4exec lead and also refer to #Rs4022s4*upporting

    documents before making a test step as 5'6. Then proper 7ustification4reason must be updated in

    the actual results column where the step is being con"erted in to 5'6.

    . 0or all 0ailed or Blocked test cases , locking De'ectcolumn in 8uality #enter must be filled with

    latest 8# 2efect no . s soon as that 8# defect gets fixed, 8# 2efect number must be remo"ed from

    defect )2 column and should be put into &De'ect ,D in (rogressfield. t that stage 2efect )2 fieldmust be blank as that 8# 2efect is resol"ed.

    .ll test cases must be executed till the step where an error occurred with proper information in

    actual result field. 0ast run of test cases must not be done.

    5.There must &e only one test run 'or any test case. 6ore than one instance is not accepta&le.

    7.ny discrepancy in any of test step from actual result must be clearly updated in description section

    and must be sa"ed after end run. *o that it will be reflected in test plan.

  • 8/9/2019 Test Execution Guidelines 1

    5/5