A Guide for Test Cases, Test Suites, Test Scripts, and Test Scenarios

[anandamalan]

A Guide for Test Cases, Test Suites, Test Scripts, and Test Scenarios

A test case is usually a single step, and its expected result, along with various additional piecesof information. It can occasionally be a series of steps but with one expected result or expected outcome.

The optional fields are a test case ID,Description,test step / 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. 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.

A Test Suit: The most common term for a collection of test cases is a test suite.

The test suite often also contains more detailed instructions / 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 test plan. They may also be called a test script, or even a test scenario.

A test plan is the approach that will be used to test the system, not the individual tests.

Most companies that use automated testing will call the code that is used their test scripts.

A scenario test is a test based on a hypothetical story used to help a person think through a complex problem or system. They can be as simple as a diagram for a testing environment or they could be a description written in prose. The ideal scenario test has five key characteristics. It is (a) a story that is (b) motivating, (c) credible, (d) complex, and (e) easy to evaluate. They are usually different from test cases in that test cases are single steps and scenarios cover a number of steps. Test suites and scenarios can be used in concert for complete system tests.

See http://www.kaner.com/pdfs/ScenarioIntroVer4.pdf

Scenario testing is similar to, but not the same as session-based testing, which is more closely related to exploratory testing, but the two concepts can be used in conjunction.

See http://www.stickyminds.com/se/S3608.asp
http://www.satisfice.com/articles/sbtm.pdf

The following links should throw some light on an organized way of approaching exploratory

testing http://www.satisfice.com/articles/et-article.pdf
What is Exploratory Testing? - James Bach - Satisfice, Inc.
Exploratory Testing and the Planning Myth - James Bach - Satisfice, Inc.
Where Does Exploratory Testing Fit? - James Bach - Satisfice, Inc.

How do I write a Test Case? What Is a Good Test Case?
http://www.stickyminds.com/r.asp?F=DART_6505

How to Write Better Test Cases
http://www.stickyminds.com/r.asp?F=DART_2136

Reducing Test Case Documentation
http://www.stickyminds.com/r.asp?F=DART_6309