Skip to content

Report and Track Issues

You can report issues in Squash TM's Campaigns workspace. You can identify and report issues during test cases executions. You can execute test cases one by one from an execution plan, or successively thanks to test suites and the button Execute.
Squash TM supports connections to Mantis, Jira (Server, Datacenter, Cloud), Redmine, Bugzilla, RTC, and Tuleap bugtrackers.

Report an Issue from an Execution Step or Execution

To execute test cases one by one, you have two options:

  • Execute them in a pop-up: an execution popup appears and enables you to execute test steps one by one.
  • New execution: the test case's execution appears and from the "Execution scenario" anchor, you can define each test step's execution result without executing them.

Test cases' execution options

You can report an issue from the "Issues" block below the execution popup, or by using the "Execution Scenario" anchor, via the button Add.
You can report a new issue by clicking on "Report new issue".

Report new issue

The page "Report a new issue" opens with the following fields to complete to report the issue in the bugtracker (example with Mantis):

  • Project: name of the project where the test case containing the issue is located. If multiple projects of the bugtracker are associated with the Squash TM project, you must choose the target project you want for the issue.

  • Category: category of the bugtracker that will enable you to categorize the issue

  • Severity: the issue's degree of severity

  • Product version: product version in which the issue was reported

  • Assigned to: person to whom the issue will be assigned

  • Summary: issue title

  • Description: By default, it contains: the description of the associated test case, the URL of the current execution, and the description of the issue, which must be completed by the user.

  • Additional information: test steps as they were entered in Squash TM until the failed test step.

When you create an issue, you must at least complete the "Summary" field. The fields filled in by default are editable.

The fields of the form depend on the project and type of issue selected by the tester. For bugtrackers other than Mantis, custom fields are also retrieved in the declare popup so they can be filled in. When you create an issue, you must complete all the fields that have an asterisk.

Report a new issue

Once you have added your issue, the "Issues" block updates itself. Your issue then appears in the table and is automatically added to the project's bugtracker. You can find it by clicking on the link in the "Key" column of the table.

Issue saved

Associate an Existing Issue with an Execution Step or Execution

When the issue observed has been reported, you can directly link it to the test step or execution by clicking on the button Ajouter and then on "Link to existing issue". Enter the issue's ID in the field, then validate your input. Once the issue is found, its information appears and it can be added to the execution step or execution.

Search for an issue

Track Known Issues for All Squash TM Items

Issues reported during an execution or from an execution are added to the "Known Issues" anchor in the test/iteration/campaign suite where the issue was found. A table with all the issues appears and the number of known issues is updated under the anchor's icon.

Thus, the "Known Issues" anchor contains all the declared issues for the test suite during the test executions contained in its execution plan. In the requirement, the "Known Issues" anchor lists all the issues associated with the tests that verify that requirement.

This table enables you to track the solving of issues ("Status" column) since the information is retrieved in real time directly from the bugtracker. It also enables you to have a complete history of the problems encountered during executions.

Known issues table

Back to top