QMetry provides Import utility to import requirements and test cases that are stored in traditional Excel format or comma separated format (CSV). Once you have access to a specific Project in QMetry, you can import such requirements/test cases with less efforts.
There are three major steps involved in import from Excel:
- Convert the requirement/test case file (XLS/XLSX/CSV) format into QMetry field format to make it compatible with QMetry.
- Import the XLSX/XLS/CSV file into QMetry by mapping the QMetry fields with XLSX/XLS/CSV columns.
- Verify that the imported requirements/test cases are displayed in QMetry as you expected.
Difference between Import and Re-import
The following table describes the difference between Import and Re-import.
|Sr. No.|| Component||Import ||Re-import|
|1||Definition||Import is creation of test assets for the first time. Import always creates version 1.||Re-import is bulk-modification of already created test assets. This saves time where bulk edit feature is not available. For requirements and test cases, re-importing will increase the existing version of requirements/test cases by 1.|
|2||Supported Formats||XLS, CSV, XLSX||XLS, CSV, XLSX|
|3||What can be imported?||1. Requirements|
2. Test Cases
|1. Requirements |
2. Test Cases
3. Test Suites - Only Executions Status
|4||What is mandatory to be mapped? ||1. Summary and All mandatory fields.|
2. Folder Paths if the assets are to be arranged in different folders.
3. Fields which are not mapped will be empty.
1. Entity Key should be mapped with ID.
2. Summary and All mandatory fields.
3. If there is no change in Folder Paths, prefer not to Map it. Map only if there are changes to folder path and you want to move assets from one folder to another.
4. For test cases/requirements, unmapped fields will be picked from previous version of the corresponding test asset.