💻Auto Testing using UI
Last updated
Last updated
Tests can be added to the Policy, when such a policy gets published then the added tests get embedded into the policy file.
Such tests are imported/exported together with their respective policies.
Note: Tests can be run only when the policy is in the dry-run or demo status.
Tests can be added to the policy via the corresponding menu option as shown on the screenshots below:
To launch a test navigate to the tests list using the ‘Test details’ menu option
Select the desired test in the grid and press Run (or Re-Run)
Note: There could be only one active (running) test per policy, multiple policies can be running tests at the same time.
Test results can be viewed in the test window
There are potential outcomes of running policy tests
Stopped – test was stopped by the user
Success – test was successfully executed and the results are fully matching those originally captured
Failure (1) – an error has occurred during the run of the test, the execution of the test was not completed
Failure (2) – test was executed, however test results (i.e. the produced artifacts) differ from those originally captured
Detailed comparison of the execution results (documents) can be performed by clicking on the ‘Show more details’ button.
Tests which are not being run can be deleted.
Tests can be managed and run from the Manage Policies grid.
This view allows to:
Add a test to the policies if it does not yet have any tests
Run the most recently added test
Re-run the most recently run test
Monitor the status of the test being run
To simplify the UI of policy testing (useful for novice users) a new ‘Demo’ mode of policy import has been introduced. In this mode all policy processing is ‘read-only’, policy editing is not possible, and no communication with external systems such as Hedera network and/or IPFS is performed. Policy execution in the Demo mode is similar to dry-run.
To use demo mode the corresponding option should be selected on the policy import dialogue.
