Last updated: Nov 22, 2018 14:00
Table of Contents
Download the Reporting SDK client for your programming language and framework
DigitalZoom Reporting Authoring
The following code changes are required to include reporting in your test:
The snippets provided below are a standalone script that does not use any execution testing framework.
Add the following require statement to the test script:
Create an instance of the reporting client
Create an instance of the ReportiumClient used to log test start/step/end events:
Optional changes (but highly recommended)
Adding reporting Tags
Add Tags are used as a freestyle text that is used for filtering in the Reporting app.
For example: .withContextTags('Test tag1', 'Test tag2', 'Test tag3')
Starting a new test
Creating a TestContext
A TestContext may be defined to include Tags and Custom Fields that are relevant to identify a specific test within a full test suite (defined by the PerfectoExecutionContext used by the PerfectoReportiumClient). The test-level tags will be added to the client-level tags associated with the test suite. The test-level Custom Fields are added to the client-level ones, overwriting any custom field values for the same key.
Adding test steps
Separate your test into actions using test steps.
Adding assertions to the Execution Report
At various points within a test execution, the script may perform verification of different test conditions. The result of these verification may be added to the Test Report by using the reportiumAssertion() method of the ReportiumClient instance. When using this method, the script includes two parameters:
- A message string - that will be used to label the assertion.
- A Boolean - indicates the result of the verification operation.
Stopping the test
When the test is completed - supply an indication of the final outcome of the test by generating a TestResult instance. The TestResultFactory class supports:
- createSuccess method - that notifies the reporting server that the test resulted in a successful status.
- createFailure method - that notifies the reporting server that the test resulted in a unsuccessful status and supports adding a notification message that is displayed in the test report.
- You can also provide a failure reason, or depend on the DigitalZoom smart analysis to identify the failure reason.
In addition to providing the status of the test result, it is possible to provide additional tags and custom fields to the test - this may be used, for example, to add indications of the paths that caused the result or the reason for stopping the test. Use the TestContext to add additional tags and custom fields:
Note: Adding the TestContext to the testStop is optional.
Getting the report URL
Browse Perfecto GitHub repo for complete Ruby Reporting samples