Test Suite Management

It is a well-known fact that test cases worth time, exertion and skills to be obtained. And it is worthwhile to spend some supplement exertion and resource to organize and manage them well.

The main part of test suite management is controlling the accumulation of the existing test cases and the new ones. It is very important to manage both of them.

Some consistent database for the test suite requires be keeping and sharing by people who are working on parallel scopes. Some specialist info may be present in the test suite as well, such as software testers who created specific test cases. This is made for better supported use of this test suite in future.

The data in the test suite composes an indexed database with weighty information about individual test cases in the test suite.

In turn actual test cases comprise more detailed data about the precise scenario, test input, anticipated result and behavior.

A lot of different methods are known to arrange the test suite or test suites. Well, the most general method is to organize them by sub-stages, because of the various objects, objectives, perspectives, priorities and the testing techniques used.

Various attributes may be used to make a description and classification of individual test cases in the suite. Here is one specific instance:

  • scenario class
  • scenario number
  • variation number with a particular scenario

The scenario class corresponds to high-level functional sets of functions. Within every scenario class, the scenario number and the variation number within every scenario number, form a three-level hierarchical formation of test cases in the suite.

Scenario number and variation number are commonly ordered in rough accordance to the anticipated implementation order. It is ranking from 1 to 99, with logical numbers used up to a point and then skipping to 99 to indicate some ad hoc test cases which do not fall into some systematic progression.

Consequently, less than 99 scenarios are permitted, which was more than respective for the product under software testing.