Known bugs in a test may be flagged, or marked. Marking
known bugs allows the fails associated with the bugs to be ignored, so that they are not
counted in test results.
- Known bugs can be marked only within test modules. The Mark As
Known Bug menu option is not available in user-defined
- A TA bug can be associated with multiple action lines in a test module;
however, a given action line may only be associated with a single TA bug at a
Ensure that the following requirements are met:
- You have sufficient privilege to mark known bugs. (Note that members of all
administration groups except guest
group do have this privilege.)
- Test modules to be edited or marked with known bugs are checked out.
- If the marked bug is to be associated with a JIRA bug, ensure that your TestArchitect test machine has registered the JIRA server.
In the TestArchitect explorer tree, double-click a test
module node to open it.
In the test module editor, do one of the following:
- Select an action line at which you want to mark a known bug, then click the
Mark As Known Bug
button on the toolbar.
- Right-click the action line to be marked, then select
In the Specify bug dialog box, enter the following
Click the Preview button to load basic information of
the bug into the Summary and
If you selected the JIRA
bug type, an
additional field, Linked to
, in the dialog box is
displayed. This field displays the TA bug associated with the selected JIRA
bug. However, if that JIRA bug is not associated with a TA bug, this field
is empty as in the figure below.
A message appears to inform you that the selected action line has been
associated with a bug successfully.
If the JIRA
bug type was selected, and that
JIRA bug is not associated with any TA bug, you are presented with the
option to create a new TA bug and import its data from the new JIRA bug:
to create a new registered TA bug associated
with that JIRA bug.
A yellow dot appears next to the newly marked line of the test:
Tip: Hover your mouse over the yellow dot to
see the screentip of the known bug. The displayed information includes
Bug ID, Source,
Marked By, Summary and
your tests, then proceed to Reviewing test result results with known bugs
verify your test results and keep track of progress on the known bugs.