That test case would end up resulting in around 10-15 steps One approach is to: Create a single test case for verifying 'Purchase of a product'from the website and, We want to test checkout feature on a website I believe it depends on the product functionality as well as the engineer's approach to QA validation. There is no hard and fast rule for assigning steps for a particular test case. In a nutshell, tests should be small & to the point, focused on testing a single requirement. I personally came across many lengthy test cases written by others that try to cover so many things and can potentially fail for multiple reasons which are confusing. Tag functional area: Have keywords to attach to your test cases related to functional modules so that it is easier to search related test cases.Īutomation mapping: If have automation in place related to the manual test case link it with unique ids for future Traceability. Traceability: When possible, link the test cases to appropriate user story or requirement by unique ids. When possible, provide the test data to be used for the test case within the test case description or with the specific test case step. Provide test data: Identifying and preparing test data can sometimes take the most time in testing. Single Pass/ Fail reason: Every test should pass/ or even fail for a single reason which is the primary objective of the test case.Īssumptions, Preconditions and Post-Conditions: Test cases should include all assumptions that apply to a test, along with any preconditions that must be met before the test can be executed. Sub- test cases : If there are some common steps/navigations then that should be abstracted out in separate sub test cases to be called out(hyperlinked) in main test cases. No Duplicate steps: There should not be any kind of redundancy between test cases in terms of steps or validations. Single Test Goal: Every test should be focused on testing a single requirement only which can be directly mapped to the acceptance criteria of the story.Ĭlarity: Every step in a test case should be clear enough so that anybody in the team can follow it. of test steps does not matter but few things matter which can make test cases highly effective:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |