Embedded Files
A new documentation is available for Squash TM 2.0 and later versions, check it here
4.2.1 Test case consultation page
4.2.1 Test case consultation page
The test case consultation page is composed of six tabs (Information tab, Script tab, Parameters tab, Attachments tab, Executions tab and Know issues tab) and of a toolbar.
4.2.2 Informations tab
4.2.2 Informations tab
The page displayed by the [Information] tab of the selected test case includes four units, "Description" unit, "Prerequisite" unit, "Requirement verified by this test case" unit, "Test case referenced by" unit.
Description unit
The Description unit displays different important pieces of information which are detailed below:
Reference (optional)
Is determined while creating the test case. Optional during the creation. It can be completed later, by clicking on the field in the test case consultation page.
Is displayed before the name in the tree structure, and is the criteria of test case organization in this tree.
Description (optional)
Is determined while creating the test case. Optional during the creation, it can be completed later by clicking on the field in the test case consultation page.
Status
Determines test case's status (it takes the value Work in progress by default), it can be changed later via the combo box.
Status can take the following values :
Work in progress
Under review
Approved
Obsolete
To be updated
Attributes unit
The Attributes unit displays different important pieces of information which detailed below:
Prerequisite unit
This unit determines a prerequisite for a given test case. It can be completed later by clicking on this field in the test case browsing page.
It is displayed in the test case execution consultation page in Campaign workspace.
Requirement verified by this test case unit
This unit enables you to associate requirement(s) with this test case.
A chapter is dedicated to this function.
Test case referenced by unit
This unit enables you to know if the selected test case has been called by another test case. This table is automatically filled in and cannot be modified.
4.2.3 Script tab (classic)
4.2.3 Script tab (classic)
The test script of a classic test case can be created via [Script]. By clicking on the tab, the user opens a script table.
A chapter is dedicated to this function.
4.2.4 Script tab (Gherkin)
4.2.4 Script tab (Gherkin)
The test script of a Gherkin test case can be edited via [Script]. By clicking on the tab, the user opens a script editor field and a help section.
A chapter is dedicated to this function.
4.2.5 Test steps tab (BDD)
4.2.5 Test steps tab (BDD)
The test script of a BDD test case can be edited via [Test steps]. By clicking on the tab, the user opens a test steps editor field and a help section.
A chapter is dedicated to this function.
4.2.6 Parameters tab
4.2.6 Parameters tab
Since the release of version 1.6.0. of Squash TM, you may add parameters to the script of your test case by clicking on [Parameters].
A chapter is dedicated to this function.
4.2.7 Attachments tab
4.2.7 Attachments tab
Click on [Attachments], an attachment table is displayed with all attachments related with the selected test case.
A chapter is dedicated to it.
4.2.8 Executions tab
4.2.8 Executions tab
Click on [Executions], a table opens up and lists the executions of the selected test case. The table is automatically filled in and cannot be modified.
Click on a link in the execution column, the consultation execution page opens up and the user can act directly on the selected execution.
A chapter is dedicated to it.
4.2.9 Known issues tab
4.2.9 Known issues tab
Click on [Known issues], a table opens up and lists the defects detected during the execution(s) of the selected test case. The table is automatically filled in and cannot be edited.
Click on the link in ID column, the related bugtracker (Mantis or Jira) opens the selected defect consultation page.
Click on the link in the column "Reported in iteration", the browsing page of the selected execution opens up.
FOCUS
The modifiable fields are available only if the user has the necessary accreditation on the project related to the test case.
Page updated
Report abuse