4.10 - Import Test case

The import/export button lets you manage all your test cases from .zip, .xls, .xlsx or .xlsm files. 

You can create, update or delete all test cases you want, but the import tables have to hold mandatory marks. 

Depending on your action, files must correspond to a project in the tree structure.


  4.10.1 Import test case from zip or xls file

To import:
  1. Reach the Test cases worskpace
  2. Click on [Import/Export] in the library toolbar (described here)
  3. Click on [Import...] in the drop down menu
  4. A pop-up window "Import Excel data" opens up:
    • Select zip/excel file by clicking on zip/excel button.
    • Click on [Choose file] and select the file to import
    • Click on [Download the import template .zip] to download a template for zip file
    • Click on [Download the import template .xls] to download a template for excel file
    • You can also choose which encoding you prefer between Windows and UTF-8 by clicking on the drop down box [Encoding] (default value is Windows, this is the most used encoding type. If you don't have to, there is no need to change it).
    • Click on [Import] to continue or [Cancel] to stop the import
    5. A confirmation pop-up window "Import Excel data" opens up, with the following information: 
    • Where your data will be read from
    • In which project your data will be uploaded
    • Click on [Confirm] if you want to proceed or [Cancel] to stop the operation
     6. A pop-up window summarizing the import opens up. It resumes how many test cases, test steps, parameters and datasets have been                          successfully uploaded or not. 
         Click on [Download import log (xls)] if you want more information from the import. 

    7. The imported test cases have been added to the tree structure, in the project mentioned in your zip/excel file.

  4.10.2 Create an import test case file, excel type

The import file must be in .xls, .xlsx or .xlsm format to be interpreted by Squash. It also must follow the different rules listed below.

If you select excel type to import your test cases, the import table needs to have five tabs with mandatory and unrequired columns (ignored columns are not mentioned in the summary tables below). Moreover, you must respect order of the tabs and columns as below.

ACTION mark management:
You must add an ACTION mark to manage test case action. If this column does not exist, the file will not be imported. To use this mark, you will need to add it in all tabs of the import file exept "LINK_REQ_TC" tab. Moreover, ACTION mark is always the first column. It also must follow the different rules listed below:

  • The file is read in order of appearance: TEST_CASES > STEPS > PARAMETERS > DATASET
  • If there are several actions in different lines of a same object, they will be dealt with in order of appearance.


To get the standard model, download "From_V1.13_Test-case_import_template_xls.xls" at the bottom of the page.

        tab 1: TEST_CASES

 MARK SIGNIFICANCE   DESCRIPTION
ACTION
 Mandatory  Mark used to put a construction on the import.
(You can add as many lines with this mark as you need to add test cases)
-> If mark is empty, the import is not going to work and the import log will tell you where the failure is.

It must hold one of these values:
  -  CREATE (C)
Test case is created with all the information mentioned in this tab. 

  -  UPDATE (U)
Test case already exists in the tree diagram. This action updates the last data, if something in the line has been changed or added (ex: name, weight,...).
-> Warning, i
f the value is UPDATE and the test case does not exist, the import is not going to work and the import log will tell you where the failure is.
 
TC_PATH
 
Mandatory 
 Test case path.
It must be completed as follows : "/project name/folder name*/test case name"
*the nale of the folder is added to the test case path only if you want to put the test case in a folder inside the project.

 TC_NUM

 Unrequired 
 Test case order inside its folder.
-> if the action value is CREATE and the mark is empty, then the test case will be positioned at the end of the folder
-> if the action value is UPDATE and the 
mark is empty, then the information will be ignored. If the mark is completed and different from the original, then the test case will be moved on to the new position. 
TC_REFERENCE Unrequired   Test case reference 

TC_NAME 

Unrequired 
 Test case name.
Unrequired 
mark because of its presence at the end of TC_PATH mark.
-> if action value is UPDATE, test case will be renamed with data informed in this 
mark.

TC_WEIGHT_AUTO
 
Unrequired 
 Test case weight calculation
 complete with 1 if weigh calculation is automatic
 complete with 0 if weigh calculation is manual 
-> if 
mark is empty, default value is 0



TC_WEIGHT
 


Unrequired 
 Test case weight type.
The values are:
  - VERY_HIGH
  - HIGH
  - MEDIUM
  - LOW
-> if 
mark is empty, default value is LOW
-> if TC_WEIGHT_AUTO = 1, the value of TC_WEIGHT will be ignored.




TC_NATURE
 



Unrequired 
 Test case nature code.
The values are:
  - ATDD
  - BUSINESS_TESTING
  - NON_FUNCTIONAL_TESTING
  - PERFORMANCE_TESTING
  - SECURITY_TESTING
  - UNDEFINED
  - USER_TESTING
-> if 
mark is empty, default value is UNDEFINED
 



TC_TYPE
 



Unrequired 
 Test case type code
The values are:
  - COMPLIANCE_TESTING
  - CORRECTION_TESTING
  - END_TO_END_TESTING
  - EVOLUTION_TESTING
  - PARTNER_TESTING
  - REGRESSION_TESTING
  - UNDEFINED
-> if 
mark is empty, default value is UNDEFINED



TC_STATUS
 


Unrequired 
 Test case status code
The values are:
  - APPROVED
  - OBSOLETE
  - TO_BE_UPDATED
  - UNDER_REVIEW
  - WORK_IN_PROGRESS
-> if 
mark is empty, default value is WORK_IN_PROGRESS
 TC_DESCRIPTION  Unrequired   Test case description
 TC_PRE_REQUISITE  Unrequired   Test case requisite
 TC_CREATED_ON  Unrequired   Test case creation date
It must be completed as follows: yyyy-mm-dd
-> if 
mark is empty, common date will be added
 TC_CREATED_BY  Unrequired   Creator login
-> if 
mark is empty, username who is importing will be used
 TC_LAST_MODIFIED_ONUnrequired
 Test case last modification date
It must be completed as follows: yyy-mm-dd
-> if mark is empty, common date will be added
 TC_LAST_MODIFIED_BYUnrequired
 Login of the last user who modified the test case
-> if mark is empty, it will be ignored
 TC_KINDUnrequired
 Test case format code:
  - STANDARD
  - GHERKIN
-> if mark is empty, the test case will be imported as a classic test case
 TC_SCRIPTING_LANGUAGEUnrequired
 Gherkin script language
 TC_SCRIPTUnrequired
 Gherkin test case script
 TC_CUF_<cuf code>  Unrequired   Test case personalized field code value <cuf code> 


    tab 2: STEPS

 MARK  SIGNIFICANCE   DESCRIPTION 
 ACTION Mandatory
 Mark used to add steps in test case.
(You can add lines with this mark as often as you want steps actions)
-> If mark is empty, step import won't work and the import log will inform what the failure is.

It must hold one of these values:
  -  CREATE (C)
Step(s) is/are created with all the information mentioned in this tab. 

  -  UPDATE (U)
steps already exist in the test case. This action updates the last data, if something in the line has been changed or added (ex: name, step number, step action or result,...).
-> Warning, i
f the value is UPDATE and the test case does not exist, the import is not going to work, and the import log will tell you what the failure is.
 TC_OWER_PATH Mandatory  Test case owner path of steps
It must be the same information completed in test cases tab (TC_PATH)
It must be completed as follows : "/project name/folder name*/test case name"

*folder name is added to test case path only if you want to put the test case in a folder inside the project
 TC_STEP_NUM Unrequired   Order of steps (by numbers)
-> if numbers are not following each other, numbers order is chosen.
-> if two steps have the same number, they are numbered in appearance order in the file.  
-> if 
mark is empty, they are numbered in appearance order in the file.
 TC_STEP_IS_CALL_STEP Unrequired  Step calling a step of another test case.
 complete with 0 if step is a step action
 complete with 1 if step is a call step
-> if mark is empty, default value is 0
 TC_STEP_CALL_DATASET Unrequired   Taken into account only if TC_STEP_IS_CALL_STEP = "1"
  • "INHERIT" if option is to not choose dataset. As a result, the calling test case inherits the called test case parameters
  • <NAME> : chosen dataset
 TC_STEP_ACTION Unrequired   Step action description or path to called test case (if it is a call step).
In the case of a call step, mark must be completed like: " CALL /projet name/file tree/.../call step name "
 TC_STEP_EXPECTED_RESULT Unrequired  Step expected result description if it's a step action
-> if TC_STEP_IS_CALL_STEP = 1, this mark is ignored
 TC_STEP_CUF <cuf code> Unrequired  Step personalized field code value <cuf code>


    tab 3: PARAMETERS

 MARK   SIGNIFICANCE  DESCRIPTION 
 ACTION Mandatory
  Mark used to add parameter(s) in test case.
(You can add lines with this mark as often as you want parameters)
-> If mark is empty, the parameter import is not going to work and the import log will tell you what the failure is.

It must hold one of these values:
  -  CREATE (C)
Parameter(s) is/are created with all the information mentioned in this tab

  -  UPDATE (U)
Parameter already exists in the test case. This action update the last data, if something in the line has been changed or added (ex: name, description, ...).
-> Warning, i
f the value is UPDATE and the test case does not exist, the import is not going to work, and the import log will tell you what the failure is.
 

TC_OWNER_PATH
 

Mandatory
 Test case owner path of parameter(s)
It must be the same information completed in test cases tab (TC_PATH)
It must be completed like : "/project name/folder name*/test case name"

*folder name is added to test case path only if you want to put the test case in a folder inside the project
 TC_PARAM_NAME  Mandatory  Parameter name.
It must only contain those characters: [0-9], [a-z], [A-Z] and [-,_].
 TC_PARAM_DESCRIPTION Unrequired  Parameter description


    tab 4: DATASETS

 MARK  SIGNIFICANCE  DESCRIPTION
 ACTION  Mandatory  Mark used to add dataset(s) in test case.
(You can add lines with this mark as often as you want datasets)
-> If mark is empty, dataset import is not going to work, and the import log will tell you what the failure is.

It must hold one of these values:
  -  CREATE (C)
Dataset(s) is/are created with all the information mentioned in this tab

  -  UPDATE (U)
Dataset already exists in the test case. This action updates the last data, if something in the line has been changed or added (ex: name, parameter name, ...).
-> Warning, if the value is UPDATE and the test case does not exist, the import is not going to work, and the import log will tell you what the failure is.
 TC_OWNER_PATH  Mandatory  Test case owner path of dataset(s)
It must be the same information completed in test cases tab (TC_PATH)
It must be completed like : "/project name/folder name*/test case name"

*folder name is added to test case path only if you want to put the test case in a folder inside the project
 TC_DATASET_NAME  Mandatory  Dataset name.
It must only contain those characters: [0-9], [a-z], [A-Z] and [-,_].
 TC_PARAM_OWNER_PATH  Unrequired  Test case owner path of parameter(s)
 
Mark is needed when parameter come from a step called by test case dataset owner.
 TC_DATASET_PARAM_NAME  Mandatory  Parameter name where the value will be informed
 TC_DATASET_PARAM_VALUE  Unrequired  value of the couple parameter/dataset 
{dataset | parameters}


    tab5: LINK_REQ_TC

 MARKSIGNIFICANCE   
 DESCRIPTION
 REQ_PATHMandatory
 Requirement path from the project name to the requirement name (current version)
NB: current name of the version can be different from the one of the version to link
 REQ_VERSION_NUMMandatory
 Number of the requirement version to link
 TC_PATHMandatory
 Test case path from the project name to the test case name

    4.10.3 Create an import test case file, zip type

Like mentioned above, the import file must be in .xls, .xlsx format to be read by Squash.

So the zip file has to contain an excel table with one tab (the name of the tab is the name of the test case you want to import), the other ones are ignored.
To import several test cases, you have to create several files (1 file = 1 tab = 1 test case)

To see the standard model, download "test-case_import_template_zip.xlsx" on the bottom of the page.

The table must hold marks in the same order as below:

 MARK FIRST VALUE  SECOND VALUE  COMMENT
 DESCRIPTION  Test case description    This value will appear in the field "Description" of the test-Case in Squash TM.
 IMPORTANCE  Test case criticality
It must hold one of these values:
  - VERY_HIGH
  - HIGH
  - MEDIUM
  - LOW.
   This field must be written in capital letters and cannot have any other value than the ones listed before (column "FIRST VALUE").
 CREATED_BY  creator's login    This value will appear in the field "Created by" of the test-case in Squash TM.
 CREATED_ON Test case creation date
 This field can be written either in date format (hour included or not)  (excel cell format) or in text format. 
In the latter case, the date must be written the following way : DD/MM/AAAA.
   This value will appear in the field "Created on" of the test-case in Squash TM.
 ACTION_STEP
(You can add this mark as often as you want steps actions)
Step action description.

 expected result  This key leads to the creation of a new Step each time it is read. Steps are created in the order of the rows (top to bottom).
 PREREQUISITES  Infos to add in the "Prerequisite" field of the Test-Case.    If several rows are marked with this key, all values will be concatenated in the "Prerequisite" field of the test-case in Squash TM.



Other rules for excel and zip files:
  • The mark is always placed on the first column
  • The value(s) are placed in the column which follow in the same line
  • The upload is made line by line, no matter the order of the lines
  • The field names of the first column are not case sensitive
  • The lines for which the first column text is not recognized as a mark will be added in the test case description (after the description itself)
  • The empty lines and formatting are ignored
  • The cells can not be merged
  • It must not have empty column between the mark column (first one) and the value column
  • It is possible to have an infinite number of cells in a line, but only the two (or three for the actions) will be taken in charge
Ĉ
Unknown user,
18 Jan 2016, 08:08
Ĉ
Unknown user,
4 Aug 2014, 06:16
Ĉ
Unknown user,
4 Aug 2014, 06:16