Generally, a test case consists of a set of conditions, variables, and/or ACTIONS being performed on a system under test to ENSURE it meets its requirements and functions properly. Good test cases INCLUDE:

• Clear OBJECTIVE: Specify the intent and scope of the test.
• Meaningful pass/fail verifications: Specifying what constitutes success and failure and how to determine both.'
• Clear and concise documentation: Prepare standardized formats for your test cases, including unique ID number, descriptions, preconditions, RELATED datasets, and expected outcomes.
• Traceability to requirements: Test cases should be traceable to requirements for a system under test. We need to ensure we test all requirements and changes, and not waste time testing irrelevant components.
• Reusability: Develop test cases that are modular and easy to maintain. It is likely that test cases will change as the system under test evolves over time, but we definitely want to write test cases that are reusable as long as possible.
• Testing of one test case independently of others: Execution of a single test case should not be dependent on other test cases. To create a larger end-to-end test, your independent, modular test cases should be able to be combined into sequential or parallel execution test suites.