Test tracking modules

In a test tracking module, you set up each object as a test case. Test case objects can be organized under headings and subheadings in the typical way. Each test case object must contain enough information in its attributes to allow a test technician to understand the requirements for the test, run the test against the product, and enter the results of the test into the object. The object can be linked to other objects in the database, for example the requirements that are being tested.
The object attributes that are used by the test technician can be split into two distinct groups:

Each time you run a test case, you need a copy of the test run attributes so that you can record the new test results. When you create a Test Run, all the Test Run Attributes are duplicated and suffixed with a number, so you can easily identify the test run that the results apply to. The original test run attributes are never used directly.

You can create a form to display the test case attributes and test run attributes of each test case. This means that when a test run is ready, the test technician can select the first test case in the module, open the form, and see immediately the background of the test case and the results that need to be recorded. The form has Next and Previous buttons so the tests can be stepped through one by one.

You can add a layout DXL column to any modules that are linked to the test module to display the status of tests linked to objects in the module as a tick or cross.

By using the test tracking tool you can build up a test history for your project, which is held together in one module.

If you are managing more complex projects, consider using formal test management tools..


Feedback