Topic: Structure of a Test Case

Message

   Structure of test case:

Formal, written test cases consist of three main parts with subsections:

    * Information contains general information about Test case.
          o Identifier is unique identifier of test case for further references, for example, while describing found defect.
          o Test case owner/creator is name of tester or test designer, who created test or is responsible for its development
          o Version of current Test case definition
          o Name of test case should be human-oriented title which allows to quickly understand test case purpose and scope.
          o Identifier of requirement which is covered by test case. Also here could be identifier of use case or functional specification item.
          o Purpose contains short description of test purpose, what functionality it checks.
          o Dependencies
    * Test case activity
          o Testing environment/configuration contains information about configuration of hardware or software which must be met while executing test case
          o Initialization describes actions, which must be performed before test case execution is started. For example, we should open some file.
          o Finalization describes actions to be done after test case is performed. For example if test case crashes database, tester should restore it before other test cases will be performed.
          o Actions step by step to be done to complete test.
          o Input data description
    *  
          o Expected results contains description of what tester should see after all test steps has been completed
          o Actual results contains a brief description of what the tester saw after the test steps has been completed. This is often replaced with a Pass/Fail. Quite often if a test case fails, reference to the defect involved should be listed in this columns

Edited by moderator - 05May2007 at 12:03am

Author	Message
vidhya Senior Member Joined: 24Mar2007 Online Status: Offline Posts: 114	Topic: Structure of a Test Case Posted: 26Mar2007 at 5:09am
	Structure of test case: Formal, written test cases consist of three main parts with subsections: * Information contains general information about Test case. o Identifier is unique identifier of test case for further references, for example, while describing found defect. o Test case owner/creator is name of tester or test designer, who created test or is responsible for its development o Version of current Test case definition o Name of test case should be human-oriented title which allows to quickly understand test case purpose and scope. o Identifier of requirement which is covered by test case. Also here could be identifier of use case or functional specification item. o Purpose contains short description of test purpose, what functionality it checks. o Dependencies * Test case activity o Testing environment/configuration contains information about configuration of hardware or software which must be met while executing test case o Initialization describes actions, which must be performed before test case execution is started. For example, we should open some file. o Finalization describes actions to be done after test case is performed. For example if test case crashes database, tester should restore it before other test cases will be performed. o Actions step by step to be done to complete test. o Input data description * o Expected results contains description of what tester should see after all test steps has been completed o Actual results contains a brief description of what the tester saw after the test steps has been completed. This is often replaced with a Pass/Fail. Quite often if a test case fails, reference to the defect involved should be listed in this columns Edited by moderator - 05May2007 at 12:03am Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged


One Stop Testing Forum : Software Testing @ OneStopTesting : Test Cases @ OneStopTesting