...
| Code Block |
|---|
#Sample command without any client configuration being provided docker run --user root --rm -it \ -v "$(pwd)/logs:/usr/o3/tr-ozone-connect/logs" \ public.ecr.aws/g5c5c6i0/tr-image/tr-ozone-connect:cbuae \ yarn tr-ozone-connect \ --formatter terse \ --loglevel-runner debuginfo \ --config /usr/o3/tr-ozone-connect/config/test-inputconfig.yaml \ --out /usr/o3/tr-ozone-connect/logs/<custom_log_file_name> |
...
| Code Block |
|---|
#Sample command WITH the client configuration being provided docker run --user root --rm -it \ -v "$(pwd)/config:/usr/o3/tr-ozone-connect/config" \ -v "$(pwd)/logs:/usr/o3/tr-ozone-connect/logs" \ public.ecr.aws/g5c5c6i0/tr-image/tr-ozone-connect:cbuae \ yarn tr-ozone-connect \ --formatter terse \ --loglevel-runner debuginfo \ --config /usr/o3/tr-ozone-connect/config/test-inputconfig.yaml \ --out /usr/o3/tr-ozone-connect/logs/<custom_log_file_name> |
...
Option | Description |
|---|---|
| If the LFI configuration is not provided, the tool will attempt to connect to a the Ozone Connect mock server deployed by Ozone in the cloud. For detailed information on the configuration file format, please refer to the configuration file section: https://openfinanceuae.atlassian.net/wiki/spaces/APIHubDocsv3APIHubDocsv4/pages/151126094168265011/Testing+Tool+User+Guide#6.2-Configuration-File SSL certificates are necessary for secure mTLS connection between the Testing Tool and LFI’s implementation of Ozone Connect. The method to generate these certificates is documented in the Certificates Generation section: https://openfinanceuae.atlassian.net/wiki/spaces/APIHubDocsv3APIHubDocsv4/pages/151126094168265011/Testing+Tool+User+Guide#6.3-Test-Certificates After generating the certificates, copy them into a folder named |
| This option is mandatory and needs to be passed to check the logs after the program has run. The logs will be available in this folder after the tests are run. |
...
Executing the Ozone Testing Tool: This 3rd part executes the Ozone Testing Tool within the container with a set of specified options:
Code Block yarn tr-ozone-connect \ --formatter terse \ --loglevel-runner debuginfo \ --config /usr/o3/tr-ozone-connect/config/test-inputconfig.yaml \ --out /usr/o3/tr-ozone-connect/logs/logs_5Aug.json
...
Step 1 | Create an input test configuration file and set up it in | Please follow the Configuration File section in order to generate the required file: https://openfinanceuae.atlassian.net/wiki/spaces/APIHubDocsv3APIHubDocsv4/pages/151126094168265011/Testing+Tool+User+Guide#6.2-Configuration-File | ||
Step 2 | Acquire/Generate the SSL certificates and put them in a | Please follow the Test Certificates section in case you need to generate test certificates: https://openfinanceuae.atlassian.net/wiki/spaces/APIHubDocsv3APIHubDocsv4/pages/151126094168265011/Testing+Tool+User+Guide#6.3-Test-Certificates Otherwise please use OFTF Certificates. | ||
Step 3 | Execute the testing tool command. |
| ||
Step 4 | The final section of the sample output, after all tests have been run and logs have been printed, will appear as follows. |
| ||
Step 5 (optional) | Review the Testing Tool output log file containing the test case results. The log file's name is specified in the last part of the command in step 1 above. You can change this name each time you run the command. If not changed, successive runs will overwrite the same file. | Use any text editor to view the file : |
...