...
The most common method for populating a repository is to use the Generate Parameterized Messages wizard when creating a test a test suite or virtual asset, but you can also structure and populate a data repository with Excel, WSDL, or schema files using the Data Repository Tool. The Data Repository Tool specifies the data to import, how to structure it, and which repository data source should be include with the imported data.
| Info | ||
|---|---|---|
| ||
|
Preparing to Import from Excel
...
Parameterizing Arrays of Varying Size in SOAtest or Parameterizing Arrays of Varying Size in Virtualize
for additional information about dsref* and ParentIndex columns.
...
- [parasoft_exclude]
- [exclude]
For details on how [parasoft_exclude] works with URL parameter data source correlations, see Matching on Absent/Empty Fields and Parameters.
Adding the Data Repository Tool
- Ensure that the Data Repository Server you want to import data into is running.
Create a new.tst file tst or provisioning action file with an empty test in or action suitein a new project or existing project. See Adding Projects, .tst files, and Test Suites or Adding Projects, Virtual Assets, and Responder Suites.
- Add a new Repository Data Source to the suite. See Creating a Repository Data Source.
Open the data source and specify the target data set for importing the data. You can browse existing repositories on the server in the Repository view (see Views in Virtualize and Views in SOAtest ). If the specified repository name or data set does not exist, it will be created at runtime.
Right-click the Test node or Action Suite node and choose Add New> Test or Action.and choose Data Repository Tool.
Click Next. and configure the data and structure initialization options. See Configuring Initialization Options.
- Click Finish and configure the Data Repository Tool.
...
| Name | Specifies the name for the node. |
|---|---|
| Data Source | Specifies the Excel workbook used to initialize the data (see Configuring Initialization Options). If the None option was enabled, this field will be empty and data will need to be added manually using the data source editor (see Viewing and Modifying the Repository Structure and Contents). |
| Sheet Name | Specifies a sheet name when importing from Excel. |
| Join Column | Specifies the name of the column used for indicating relationships across Excel sheets. By default, the ParentIndex column is used (see Defining the Structure). If the value in a record’s Join Column matches the value in a Parent Join Column record, then that record becomes a child of the parent record. This setting is not available for column-level nodes. This setting cannot be configured for worksheet-level nodes at the root of the tree. |
| Parent Join Column | Specifies the column in the parent node used for indicating relationships across Excel sheets. By default, the value is set to <Row Number>, which specifies that the column correlates to the parent row number. If the value in a record’s Join Column matches the value in a Parent Join Column record, then that record becomes a child of the parent record. This setting is not available for column-level nodes. This setting cannot be configured for worksheet-level nodes at the root of the tree. |
| Data Column | Specifies name of the column containing the data. |
| Field Type | Specifies which type the data should be imported as. You can specify one of the following types:
See Viewing and Modifying the Repository Structure and Contents for additional information about types. |
Specifying Data Set Keys
Data set keys allow you to specify key columns that will be used for Virtualize responder correlations. These columns can later be selected in the Data Source Correlations tab.
If you don’t specify these key columns now, you can add them later in the Data Editor.
See Responder Correlation Tab for additional information.
Running the Tool
Select the Data Repository tool that and click Run in the toolbar.
Details on the import will be reported in the Console view.
...
Any problems with the import will be reported in the progress view. For instance, the following message might occur if you are trying to import data into a Repository Server that is not currently running.
