CSV Data Import User Guide for VERA 2 with Micro Focus QC/ALM

Size: px

Start display at page:

Download "CSV Data Import User Guide for VERA 2 with Micro Focus QC/ALM"

Nickolas Simpson
5 years ago
Views:

1 for VERA 2 with Micro Focus QC/ALM Document ID: Tx GUI.052 Document Version: 01 Issued: November 1, 2018 Tx3 Services, LLC 980 Harvest Drive Suite 205 Blue Bell, PA 19422

2 Table of Contents 1. Importing data from CSV Preparing CSV file Requirement Header Test Header Importing Requirements and Requirement Traceability Importing Tests Importing Test Coverage Updating Requirements and Tests using IDs Known Issues and Limitations Tx3 Services, LLC Page 2 of 20

3 1. Importing data from CSV CSV files are text files representing tabular data that can be imported into VERA ALM Projects as Requirements or Tests. 2. Preparing CSV file Utilize Microsoft Excel to prepare a data file to import requirements or tests. Save the file as a comma separated value (.csv) file. Each CSV file must contain a header row that maps to ALM field labels. Each additional row represents a requirement, test or test step. The file must include the requirement name, test name and any required fields for requirement type or test. For each requirement, include data for the required fields of the specific requirement type. Additional fields can be included as columns as well. The standard VERA headers for each entity are below. This does not include customer specific configuration changes Requirement Header Requirement Header Required Description Path No In the Path column, enter the path under which the requirement is created. Separate each hierarchical level with a backslash (\) character. The hierarchy must be created or imported prior to creating child requirements. If a Path value is omitted on a given row, then the importer will default to the last-defined Path value from a previous row. If no previous row has a defined Path value, then the requirement will be imported under the root Requirement in the Requirements module. Note: The Path column is a required column, even though a value in each row is not required. Name Yes Enter Requirement Name, a requirement name cannot include the following characters: \ ^ * The requirement name must be unique in the requirement path. Author Yes Enter an active project username in the Author field. Description No Enter Requirement description in Description field. You can also include html tags for formatting. Requirement Type Yes For each requirement, specify the requirement type GxP Yes 1 Enter Y or N in GxP column Trace To No You can create a Trace To requirement relationship by entering one or more requirements in the Trace To column. Enter a line break list of Requirement IDs or Requirements (Path and Name). The Trace To requirement(s) must be created or imported prior to using Trace To column. You can also use an asterisk with the Requirement path to include all requirements in the path. Trace From No You can create a Trace From requirement relationship by entering one or more requirements in the Trace To column. Enter a line break list of Requirement IDs or Requirements (Path and Name). The Trace From requirement(s) must 1 GxP field is not required for Folder requirement types in Standard VERA configuration. Tx3 Services, LLC Page 3 of 20

4 Requirement Header Required Description be created or imported prior to using Trace From column. You can also use an asterisk with the Requirement path to include all requirements in the path. Tests No You can create test coverage by entering one or more Test IDs in the Tests column. Enter a line break list of Test IDs. The Test(s) must be created prior to using Tests column. Target Release No Enter the Release ID in the Target Release column. The release must be created prior to import. Multiple releases are associated with a requirement by entered a line break list of releases Target Cycle No Enter the Cycle ID in the Target Cycle column. The user must enter the associated Release ID when they enter a Target Cycle. The cycle must be created prior to import. Multiple cycles are associated with a requirement by entered a line break list of cycles 2.2. Test Header Test Header Required Description Subject Yes In the Subject column, enter the path under which the test is created. Separate each hierarchical level with a backslash (\) character. The hierarchy must be created or imported prior to creating child tests. Name Yes Enter Test Name, A test name cannot include the following characters: \ / : "? < > * % ' The test name must be unique in the subject folder. Designer Yes Enter an active project username in the Designer field. Description No Enter Test description in Description field. You can also include html tags for formatting. Type Yes For each test, specify the test type GxP Yes Enter Y or N in GxP column Category Yes Enter a valid category available in the field dropdown list Test Goal No Enter a valid test goal available in the field dropdown list [Step]Step Name No Enter a step name using the ALM format: Step # Note: The following Test Step fields must be included to import a test step: Step Name, Description, and Expected Result [Step]Description No Enter Test Step description in Test Step Description field. You can also include html tags for formatting. [Step]Expected Result No Enter Test Step description in Test Step Description field. You can also include html tags for formatting. [Step]Evidence Required No Enter Y or N in Test Step Evidence column Note: The following Test Step fields must be included to import a test step: Tx3 Services, LLC Page 4 of 20

[Step]Step Name [Step]Description [Step]Expected Result 3. Importing Requirements and Requirement Traceability The Requirement Author can import requirements from a CSV file.

5 [Step]Step Name [Step]Description [Step]Expected Result 3. Importing Requirements and Requirement Traceability The Requirement Author can import requirements from a CSV file. If a new requirement is imported, VERA will set the default values for the following fields. These fields should not be included in the CSV file. This does not include customer specific configuration changes. Requirement Field Status Revision Reason 1 Default Value Draft Existing Requirements can be modified by the CSV Data Import provided the requirement is in the correct status for field updates. VERA will enforce the Records Management Policy and prevent updates to fields controlled by status. Setup your CSV File with Requirements Figure 1: Example of Requirements in a CSV file. CSV data is imported by clicking the VERA Import Utility button in the Requirements module toolbar. Figure 2: Example of the 'VERA Import Utility' button in the QC/ALM Requirements module. Tx3 Services, LLC Page 5 of 20

6 Figure 3: Select Import File example Figure 4: Import Summary example Tx3 Services, LLC Page 6 of 20

7 Figure 5: Progress bar example Figure 6: Import Results example Tx3 Services, LLC Page 7 of 20

8 Figure 7: QC/ALM with imported requirements example Figure 8: QC/ALM with imported requirement traceability example Tx3 Services, LLC Page 8 of 20

4. Importing Tests The Test Designer can import tests from a CSV file. If a new test is imported, VERA will set the default values for the following fields.

9 4. Importing Tests The Test Designer can import tests from a CSV file. If a new test is imported, VERA will set the default values for the following fields. These fields should not be included in the CSV file. This does not include customer specific configuration changes. Requirement Field Status Revision Reason 1 Default Value Draft Existing Tests can be modified by the CSV Data Import provided the test is in the correct status for field updates. VERA will enforce the Records Management Policy and prevent updates to fields controlled by status. Setup your CSV File with Tests Figure 9: Example of Tests in a CSV file. CSV data is imported by clicking the VERA Import Utility button in the Test Plan module toolbar. Figure 10: Example of the 'VERA Import Utility' button in the QC/ALM Test Plan module. Tx3 Services, LLC Page 9 of 20

10 Figure 11: Select Import File example Figure 12: Import Summary example Tx3 Services, LLC Page 10 of 20

11 Figure 13: Progress bar example Figure 14: Import Results example Tx3 Services, LLC Page 11 of 20

12 Figure 15: QC/ALM with imported test example Figure 16: QC/ALM with imported test steps example 5. Importing Test Coverage The Requirement Author can import test coverage from a CSV file provided the tests exist in QC/ALM and the Requirement is in a state that the Records Management Policy allows updates to test coverage. Setup your CSV File with Requirements and Test IDs Tx3 Services, LLC Page 12 of 20

Figure 17: Example of Requirements with Test Coverage in a CSV file. CSV data is imported by clicking the VERA Import Utility button in the Requirements module toolbar.

13 Figure 17: Example of Requirements with Test Coverage in a CSV file. CSV data is imported by clicking the VERA Import Utility button in the Requirements module toolbar. Figure 18: Example of the 'VERA Import Utility' button in the QC/ALM Requirements module. Figure 19: Select Import File example Tx3 Services, LLC Page 13 of 20

14 Figure 20: Import Summary example Figure 21: Progress bar example Tx3 Services, LLC Page 14 of 20

15 Tx3 Services, LLC Page 15 of 20

16 Figure 22: Import Results example Figure 23: QC/ALM with imported test coverage example Tx3 Services, LLC Page 16 of 20

Figure 24: Export data from QC/ALM example Figure 25: save exported data from QC/ALM example Insert Path

17 6. Updating Requirements and Tests using IDs Requirement Authors and Test Designers can export data from the QC/ALM Grid view, update in Excel and import changes to QC/ALM with CSV Data Import. Figure 24: Export data from QC/ALM example Figure 25: save exported data from QC/ALM example Insert Path column and update the Req ID header to ID to update existing requirements without the path. Tx3 Services, LLC Page 17 of 20

18 Figure 26: updated csv file example CSV data is imported by clicking the VERA Import Utility button in the Requirements module toolbar. Figure 27: Example of the 'VERA Import Utility' button in the QC/ALM Requirements module. Figure 28: Select Import File example Tx3 Services, LLC Page 18 of 20

19 Figure 29: Import Summary example Figure 30: Progress bar example Tx3 Services, LLC Page 19 of 20

Known Issues and Limitations Importing attachments is

20 Figure 31: Import Results example Figure 32: QC/ALM with updated requirements from import example 7. Known Issues and Limitations Importing attachments is not supported. Tx3 Services, LLC Page 20 of 20

Overview The Auto Number functionality allows users to configure auto numbering on an Attribute for a specific Entity within Dynamics 365.

Overview The Auto Number functionality allows users to configure auto numbering on an Attribute for a specific Entity within Dynamics 365. An Auto Number Header will need to be created. This allows you