A test case is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements or works correctly. It usually is a document, which has a set of test data, preconditions, expected results and postconditions, developed for a particular test scenario in order to verify compliance against a specific requirement.
This instructions are inetended to give you a better scope of what a good Test Case could be like rather than a sole resource for the artifact of your project. You may need to tailor it and make several other changes to ensure it is a good fit for your use and project.
Title and Number: Using a few key words that fit the test case to be described. Description: High level overview of the test case capability provided. Priority: The importance of the test case to the application. Status: The condition of the test case described. User Goal: High level achievement or purpose of the functionality provided. (What problem are we trying to solve?) Desired Outcome: User Goal achieved. Dependent Test Cases: The list of Test Case numbers for functionality that must exist before the described functionality in current Test Case can be performed. Requirements: A cross reference listing of the portions of functionality the system must implement relating to this Test Case. These are often the "The system shall" statements in the Test Case steps. Pre-conditions: The actions of the user or of the system that must have occurred in order for the functionality to be provided. Preconditions do not include steps in the Test Case Workflow. Post-conditions: The changes to the system after the user completes the Test Case Workflow. Trigger: The catalyst or motivation causing the user to use the Test Case functionality. This does not involve steps in the using the system. Workflow: The steps involved in using the system to provide the desired functionality. The steps are typically a series of steps listing an exchange of "The user shall..." followed by "The system shall..." The steps can refer to steps in other Test Cases. The starting point is after Pre-Conditions.i Alternate Workflow: The steps involved in alternate functionality and error processing.