Test Case is nothing but it shows your defined activities and steps which you will perform in your testing.
In Manual testing test case is written manually but in automation testing it is generated by testing tools and is known as Test Script. Test Case and Test Script both are same because both of them perform same activities but has only one difference that test case is written in simple sentences and test script is generated in form script. Script is light weight programming language.
Test case Format:
Test case ID: Unique ID for each test case. Follow some convention to indicate types of test. E.g. ‘TC_Module_SubModule_01′
Test priority (Low/Medium/High): This is useful while test execution. Test priority should be set by reviewer.
Module Name – Mention name of main module or sub module.
Test Designed By: Name of tester
Test Designed Date: Date when wrote
Test Executed By: Name of tester who executed this test. To be filled after test execution.
Test Execution Date: Date when test executed.
Test Objective/Description: Describe test objective in brief.
Pre-condition: Any prerequisite that must be fulfilled before execution of this test case. List all pre-conditions in order to successfully execute this test case.
Dependencies: Mention any dependencies on other test cases or test requirement.
Test Steps: Write every Action and corresponding result in Expected Result
Test Data: Use of test data as an input for this test case.
Expected Result: Describe the expected result in detail including message/error that should be displayed on screen for your every action.
Post-condition: What should be the state of the system after executing this test case?
Actual result: Actual test result should be filled after test execution.
Status (Pass/Fail): If actual result is not as per the expected result mark this test as failed. Otherwise update as passed.
Notes/Comments/Questions: To support above fields if there are some special conditions which can’t be described in any of the above fields or there are questions related to expected or actual results mention those here.
Add following fields if necessary:
Defect ID/Link: If test status is fail, then include the link to defect log or mention the defect number.
Test Type/Keywords: This field can be used to classify tests based on test types. E.g. functional, usability, business rules etc.
Requirements: Requirements for which this test case is being written. Preferably the exact section number of the requirement doc.
Attachments/References: This field is useful for complex test scenarios. To explain test steps or expected result using a visio diagram as a reference. Provide the link or location to the actual path of the diagram or document.
Automation? (Yes/No): Whether this test case is automated or not. Useful to track automation status when test cases are automated.
In Manual testing test case is written manually but in automation testing it is generated by testing tools and is known as Test Script. Test Case and Test Script both are same because both of them perform same activities but has only one difference that test case is written in simple sentences and test script is generated in form script. Script is light weight programming language.
Test case Format:
Test case ID: Unique ID for each test case. Follow some convention to indicate types of test. E.g. ‘TC_Module_SubModule_01′
Test priority (Low/Medium/High): This is useful while test execution. Test priority should be set by reviewer.
Module Name – Mention name of main module or sub module.
Test Designed By: Name of tester
Test Designed Date: Date when wrote
Test Executed By: Name of tester who executed this test. To be filled after test execution.
Test Execution Date: Date when test executed.
Test Objective/Description: Describe test objective in brief.
Pre-condition: Any prerequisite that must be fulfilled before execution of this test case. List all pre-conditions in order to successfully execute this test case.
Dependencies: Mention any dependencies on other test cases or test requirement.
Test Steps: Write every Action and corresponding result in Expected Result
Test Data: Use of test data as an input for this test case.
Expected Result: Describe the expected result in detail including message/error that should be displayed on screen for your every action.
Post-condition: What should be the state of the system after executing this test case?
Actual result: Actual test result should be filled after test execution.
Status (Pass/Fail): If actual result is not as per the expected result mark this test as failed. Otherwise update as passed.
Notes/Comments/Questions: To support above fields if there are some special conditions which can’t be described in any of the above fields or there are questions related to expected or actual results mention those here.
Add following fields if necessary:
Defect ID/Link: If test status is fail, then include the link to defect log or mention the defect number.
Test Type/Keywords: This field can be used to classify tests based on test types. E.g. functional, usability, business rules etc.
Requirements: Requirements for which this test case is being written. Preferably the exact section number of the requirement doc.
Attachments/References: This field is useful for complex test scenarios. To explain test steps or expected result using a visio diagram as a reference. Provide the link or location to the actual path of the diagram or document.
Automation? (Yes/No): Whether this test case is automated or not. Useful to track automation status when test cases are automated.
No comments:
Post a Comment