Interested to Buy Any Domain ? << Click Here >> for more details...
Answer Posted / sandeep
Utility Value: The first thing to review in a test case is its utility value. Is this test case required? Is this testing something which has already been covered in some other test case? Is this testing something too little? There has to be definite value which this test case provides. And it should test a requirement or feature which is mentioned in the specifications of the system.
Test Case Objective: When you go through the test case for review, check if you are able to understand the objective of the test case. A good test case should have a single objective. In case there are multiple objectives that are being tested, then you should recommend that the complex test case be broken down into more simple test cases.
Pre-Requisites: Does the test case require any special setup to be done before execution? Is there any action to be taken before-hand? Has this been mentioned clearly in the test case?
Steps: Does the test case contain step wise instructions to be followed for executing the test case? Can a new tester attain the objective by following the test steps? If not, then the test case writer is presuming some steps, and has missed to put in the necessary steps in the test case.
Inputs: The test case should clearly specify what values to be given as inputs in the test case. Nowhere should it have instructions mentioning, enter any number, or string, as that may cause the test case to return different results every time.
Language: The language used in the test case should be simple and unambiguous. There should be no scope for interpreting the test case in any other manner except the desired one.
Results: A good test case should clearly mention what is the expected result and behaviour of the system. Determination of whether the test passes or fails should be fairly straight forward.
Clean-up: If the test case has changed the state of the system in such a way that subsequent test cases may get affected, then it should have steps which undo these changes to ensure there is no impact on the subsequently executing tests.
Dependencies: Does this test case have any dependencies with any other test cases? Are they to be executed before or after this test case? If yes, this too needs to be clearly documented in the test case. Ideally every test case should have its own individuality with no dependencies on others. Where it cannot be avoided, then it should be documented very clearly.
Documentation: A test case should clearly mention the name of the author, the test case priority (if applicable), and the specific requirement which it tests so as to help in doing traceability to find out the test coverage.
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
Hi Team, I have two scenarios ,only one step alone deference betweeen them and preconditions of Test scenarios are defferent . In the above sutuation , are we going divide test cases into two or can we club into them into a single. Regards seshu
how to write a test cases for Quick links like Feedback/Suggestions Advertise with us Contribute Invite a Friend FAQs Make HomePage RSS Feed Buzz Words Email Privacy Statement Terms & Conditions Copyright Disclaimer Download Forgot Password
how to write test case on gmail for TO field in compose page? only for the particular field.what will different type of user do with it like student,doctor?
Explain the integration testing?
How can we write a good test case?
What is component testing?
Suppose a job should be executed for every two hours? Write test case for this?
If there are 3 modules what would be test for that three modules but that 3 modules are not developed or what are the test case for that 3 modules
can you tell me how to write test cases for payments, receipts, inward clearing, outward clearing, A/c statements ?
They were asking sily questions and definitions rather than practical experience related questions. More focused on Definitions.
Write test cases for this scenario if a job fails it should get restarted again this should happen for three times if it fails again then it should quit?
Can someone help to write testcase for the scenario as early as possible.: 1. Complaint logged since one week 2. complaint info sent to supervisor with high priorit mail 3. 10 users logged into website , performance could not be degraded ( response within 5 seconds) 4. site should be user protected. 5. it should be work with IE 6 IE 7 6. complaint log should be generated more than one week
Explain the exactly meaning of test case?
Write the test case for a login page?
How to write email id in world wide web
