A http://en.wikipedia.org/wiki/Test_case - test case is a software testing document,which consists of event,action,input,output,expected result and actual result. Clinically defined (IEEE 829-1998) a test case is an input and an expected result. This can be as pragmatic as 'for condition x your derived result is y', whereas other test cases described in more detail the input scenario and what results might be expected. It can occasionally be a series of steps (but often steps are contained in a separate test procedure that can be exercised against multiple test cases, as a matter of economy) but with one expected result or expected outcome. The optional fields are a test case ID, test step or order of execution number, related requirement(s), depth, test category, author, and check boxes for whether the test is automatable and has been automated. Larger test cases may also contain prerequisite states or steps, and descriptions. A 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.

The term http://en.wikipedia.org/wiki/Test_script - test script is the combination of a test case, test procedure and test data. Initially the term was derived from the byproduct of work created by automated regression test tools. Today, http://en.wikipedia.org/wiki/Test_script - test scripts can be manual, automated or a combination of both.

The most common term for a collection of test cases is a http://en.wikipedia.org/wiki/Test_suite - test suite . The test suite often also contains more detailed instructions or goals for each collection of test cases. It definitely contains a section where the tester identifies the system configuration used during testing. A group of test cases may also contain prerequisite states or steps, and descriptions of the following tests.

Collections of test cases are sometimes incorrectly termed a http://en.wikipedia.org/wiki/Test_plan - test plan . They might correctly be called a test specification. If sequence is specified, it can be called a http://en.wikipedia.org/wiki/Test_script - test script , http://en.wikipedia.org/wiki/Scenario_test - scenario or procedure.