features of an application. An expected result or expected outcome is usually given. Additional information that may be included: Test Case ID - This field uniquely identifies a test case. Test case Description/Summary - This field describes the test case objective. Test steps - In this field, the exact steps are mentioned for performing the test case. Pre-requisites - This field specifies the conditions or steps that must be followed before the test steps executions. Test category Author- Name of the Tester. Automation - Whether this test case is automated or not. Pass/fail Remarks Larger test cases may also contain prerequisite states or steps, and descriptions. A written test case should also contain a place for the actual result. These steps can be stored in a word processor document, spreadsheet, database or other common repository. In a database system, you may also be able to see past test results and who generated the results and the system configuration used to generate those results. These past results would usually be stored in a separate table. Test suites often also contain Test summary Configuration Besides a description of the functionality to be tested, and the preparation required to ensure that the test can be conducted, the most time-consuming part in the test case is creating the tests and modifying them when the system changes. Under special circumstances, there could be a need to run the test, produce results, and then a team of experts would evaluate if the results can be considered as a pass. This happens often on new products' performance number determination. The first test is taken as the base line for subsequent test and product release cycles. Acceptance tests, which use a variation of a written test case, are commonly performed by a group of end-users or clients of the system to ensure the developed system meets the requirements specified or the contract. User acceptance tests are differentiated by the inclusion of happy path or positive test cases to the almost complete exclusion of negative test cases. See also Classification Tree Method References External links Writing Software Security Test Cases - Putting security test cases into your test plan by Robert Auger Software Test Case Engineering By Ajay Bhagwat Software testing