Embedded Files
A new documentation is available for Squash TM 2.0 and later versions, check it here
General principles:
General principles:
Excel files (.xls or .xlsx) are mandatory to import links between requirements and test cases.
To import a link:
Go to either requirements or test cases space,
2. Click on the third button on top of the tree (import),
3. Click on the 'Import Links' in the scrolls down menu,
4. An 'Import Excel data' pop-up opens up, in which you can:
Choose the excel file by clicking on 'Browse',
Then click in 'Import'.
5. A pop-up appears indicating:
The name of the imported file.
Click on [Ok] or (Cancel] to stop the operation.
6. If the files passes the first preliminary checks, a window summing-up the import appears. Click on [Ok].
7. Imported links appears inthe dedicated blocks on the consultation pages of requirements and test cases.
A blank link import file is available for download in attached files: blank_template_import_association.xlsx
Mandatory rules to build the Excel file:
Mandatory rules to build the Excel file:
The imported Excel file must contains a table with the following columns.
The first tab only will be imported, all others will be ignored.
Requirements' version number as well as requirements and test cases ID must already be existing in Squash TM.
Imported data will be materialized by a marker/value.
All markers must be placed on the first row, in whichever order.
All values are placed in rows below.
Import is made row by row in whichever order..
First row fields are not case sensitive.
Blank rows are not interpreted.
Cells must not be merged.
Exception handled by Squash TM:
Exception handled by Squash TM:
The obsolete version of a requirement cannot be linked to a test case.
An already existing link between a requirement and a test case.
A requirement version does not exist in Squash TM.
A requirement ID does not exist in Squash TM.
A test case ID does not exist in Squash TM.
Description of the links import table:
Description of the links import table:
ID_REQ
Write here the requirement ID
VERSION
Write here the requirement version
ID_TC
Write here the test case ID
Page updated
Report abuse