Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

This page describes some common tasks for maintaining the script test system.

Add/Remove Bugs

Add bugs to failing tests

Every test that is listed as failing should have a bug ID listed next to it, like so:

Target_DC_Max_Iterations_Display (script) [ptrn
1,2,3 failed] [GMT-3130]

In this example, the components are:

  • Target_DC_Max_Iterations_Display - test name
  • (script) - run mode (e.g. script, save, function)

  • [ptrn 1,2,3 failed] - failure message

  • [GMT-3130] - bug ID

If a test is failing and does not have a bug ID associated with it, add it with the tcfile utility:

>> tcfile('Cases', {'casename'}, 'AddBugs', {'GMT-####'}); 

You can add multiple bugs or multiple cases this way:

>> tcfile('Cases', {'case1', 'case2', 'case3'}, 'AddBugs', {'GMT-####', 'GMT-####'});

Remove bugs from passing tests

If a test is passing and still has a bug ID associated with it, the test will appear in the Test System Warnings section. These tests need to be untagged:

 >> tcfile('Cases', {'casename'}, 'RemoveBugs', {'GMT-####'});

You can remove multiple bugs from multiple cases this way:

>> tcfile('Cases', {'case1', 'case2', 'case3'}, 'RemoveBugs', {'GMT-####', 'GMT-####'});
  • No labels