Page History
With the Blueriq Model Mapper Encore it is possible to create and run test cases for Data Mappings. This Command Line Interface Test Runner is created to run the created tests in a Continuous Integration/ Continuous Deployment environment to enhance the quality control of your Blueriq Models. When the Test Runner is ran the test results are stored in a file which can be interpreted by a CI/CD like Jenkins. The file output format follows the Apache Ant's JUnit task XML Schema, which is widely used by different reporting tools.
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
C:\modelblueriq-mapperencore\cli-test-runner-win.exe --proxyServerUrl=http://localhost:1337 --studioUsername=username --studioPassword=password --repository=MyRepository --branch=Trunk --projects=MyProject1,MyProject2 |
When this configuration is used and the Test Runner has been executed, the test results will we available at C:\modelblueriq-mapperencore\target\TestResults-MyProject1.xml. Another way to execute the Test Runner is via configuration file, which can be used to pass in the command line arguments. An example of such configuration file would look like this.
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
C:\modelblueriq-mapperencore\cli-test-runner-win.exe --config=config.json |
...
| Argument | Required | Explanation | Default value |
|---|---|---|---|
| --proxyServerUrl | yes | The url of the proxy server(NGINX) of the Model MapperBlueriq Encore Example: http://myurl:port/ | - |
| --studioUsername | yes | The studio username which is used to retrieve information from Blueriq Studio | - |
| --studioPassword | yes | The studio password which is used to retrieve information from Blueriq Studio | - |
| --repository, -r | yes | The studio repository which is used to retrieve information from Blueriq Studio | - |
| --branch, -b | yes | The studio branch which is used to retrieve information from Blueriq Studio | - |
| --projects, -p | no | The studio projects which are used to retrieve information from Blueriq Studio, when not provided all projects are retrieved | - |
| --outputDir | no | The output directory where the ouput file will be created in | <currentDirectory>/target |
| -c ,--config | no | The location of a JSON config file containing configured test runner argument | - |
Overview
Content Tools