JSON Create Template
Search Knowledge Base by Keyword
Component Overview JSON Create Template
Flow Location
C:\VIPTDM\ParseXMLJSon\json_to_template
Submit through Executor Form
No
Use as part of models and TDA
Yes
Used in Solutions
Template
Operation – JSON Create Template 1 – Initial scan
Parse JSon to get a control file.
Parameters
Parameter | Description | Internal |
parJSonFilePath | The path to the input Json. Example input:“C:\VIPTDM\ParseXMLJSon\json_to_template\POSTPet.json” |
N |
parCSvPathControl | This is the control filePath that controls where files are output . The user may specify a folder where the output control csv is “parCSvPathControl /control_[input filename].csv” or just specify the full csv filePath for output using this parameter.
Example input: “C:\VIPTDM\ParseXMLJSon\json_to_template\” or “C:\VIPTDM\ParseXMLJSon\json_to_template\control_POSTPet.csv” |
y |
parMode | “parse” because we are doing the initial scan. |
Table 1: Parameters for JSON Create Template 1 – Initial Scan solution.
Output Data
A control file looks like this:
Figure 1: Control file
How to use the Component for creation of Control File
Firstly the parameters must be populated as shown in Table 1 . Then a user can run the process from VipExecutor/TemplateManagement/JSON Create Template – 1 – Initial Scan. The user also needs to provide the JSON example file. This is shown in Figure 2.
Figure 2: UI for the example file entry.
After execution the Control file is returned like in Figure 1 and is also created in the parCSvPathControl file path.
Operation – JSON Create Template 2 – Create Template
Use Json input file with Control file to get a Template file from the original Json.
Parameters
Parameter | Description | Internal |
parJSonFilePath | The path to the JSON. Example input:“C:\VIPTDM\ParseXMLJSon\json_to_template\POSTPet.json” |
N |
parVariationType | Do we want to take data values with csv or use parameters
Example input: “csv” or “parms” |
y |
parCSvPathControl | This is the control filePath that control files are read from/to. The user must specify the full csv file path to read from.
Example input: “C:\VIPTDM\ParseXMLJSon\json_to_template\control_POSTPet.csv” |
y |
parTemplateFilePath | This is the filepath where the template is output. The user must populate this with a folder and the created template will have the path folder/[input filename].template. | y |
Table 2: Parameters for JSON Create Template 2 solution.
Output Data
The output data is a template file like this:
Figure 3 : Example template
How to Use the component for creation of template
Firstly the parameters must be populated as shown in Table 2 . Then a user can run the process from VipExecutor/TemplateManagement/JSON Create Template – 2. The user needs to provide the JSON example file and control csv file shown in Figure 4.
Figure 4: UI for the example file entry.
After execution, a template file like the one in Figure 3 is returned and also created in parTemplateFilePath.
-
-
-
- IEnumerable to Data Reader
- Data Table to List
- Nested String List to Data Table
- List to Data Table
- IEnumerable to List
- List to IEnumerable
- Remove from List
- Exists in List
- Value Exists in Dictionary
- Key Exists in Dictionary
- Remove from Dictionary
- Get from Dictionary
- Clear Dictionary
- Add to Dictionary
- Clear List
- Add to List
- Show all articles ( 1 ) Collapse Articles
-
-
-
-
- Explanation of Remaining Sheets in the Control Spreadsheet (for reference only)
- The ForeignKeys Sheet - Specifying which Foreign Keys to read from the Source Database
- The Tables Sheet: Defining Metadata that will be read from the Source Database
- The ProcessModel sheet – Toggling Subset Rules
- Refining the Control Spreadsheet
- Overview of the Advanced Control Spreadsheet
- Introduction
-
- Drop both Primary and Foreign Keys (The composite DROPKEYS Action)
- Validate Both Primary and Foreign Keys (The composite ValidateKeys Action)
- Add Both Primary and Foreign Keys (The Composite ADDKEYS action)
- Drop Tables
- Truncate Data
- Delete Orphans
- Drop Primary Keys
- Drop Foreign Keys
- Validate that Foreign Keys are Unique
- Validate that Primary Keys are Unique
- Add Foreign Keys
- Add Primary Keys
- Overview of Post-Subset Actions
-
-
- Use Event Hooks to call VIP Flows
- Different Methods for Connecting to Source Databases
- PreProcess Variables and Parameters
- Using SQL Functions to query Databases and Using the Queries in Data Generation Functions
- Summary of the Process to Configure the Test Data Configuration sheet
- How the PreProcessVariables Table is used in the Configuration sheet
- Sample Commerce Configuration Sheet Examples
- Adding Event Hooks in Configuration sheet for custom functionality
- How to Configure the Synthetic Test Data Configuration Control Sheet
-
-
-
-
-
- The UI Recorder
- Test Modeller – Maintenance
- Test Modeller Core (Linux) Optional – Postgres LDAP
- Test Modeller Core (Linux) Optional – SSL Certificate Installation
- Test Modeller Core (Linux) Optional – Active Directory
- Test Modeller Core (Linux) Installation
- Test Modeller: Software Pre-requisites
- Test Modeller : Installation components
- Test Modeller : System requirements (Windows, Linux)
-
-
-
-
-
-
- Common Problems
- Extend Test Modeller (Advanced)
- Edit Code Templates (Advanced)
- Import existing framework / custom page objects (Advanced)
- Execute Tests (Java)
- Generate Automation Code
- Build a Model (Java)
- Scan an Existing Web App
- Configuration (Java)
- Prerequisites (Selenium Java)
- Welcome Selenium (Java)
-
-
-
-
- Generate Optimised Test Cases and Data into Excel
- Implement Naming Conventions
- Page Object Generation
- Intelligent Page Objects
- Customising Page Objects
- Import Custom Code Snippets
- Rule-Based Test Generation
- Trigger Automation Execution from within Test Modeller
- Automation Configuration
- Test Data Automation for Gherkin Specifications
-
-