Last updated: Feb 17, 2020 18:57
Upgrade the project to version 1.20
Make sure you are on version 1.19.
Make sure the listed version of the reporting SDK is 2.3:
Change the following versions:
- If you use Eclipse, perform the Maven update by selecting the force snapshot release.
Make use of new features
The multiple-device reports and custom tags in Smart Reporting features introduced in version 1.20 require configuration before you can use them. This section walks you through the necessary changes.
Multiple-device integration with Smart Reporting
- Make sure you use
DriverUtils.switchToDriver(String driverName)instead of the custom methods used in individual projects. This is required for multiple-driver Smart Reporting results and proper device IDs in console logs.
driverNameListparameter with all driver names as a comma-separated string in the TestNG configuration, as shown in the following code snippet:
When using the
driverNameas the parameter in the
switchToDriver()method or in the
driverNameListparameter in TestNG, make sure value for
driverNameuses only lowercase letters.
The Appium driver that is used for mobile application testing uses the following driver names:
The Remote Web Driver that is used for desktop or mobile browser testing use the following driver names (note the
The following image shows an example for the final report.
Custom fields in Smart Reporting
You can now use custom fields in Smart Reporting by means of tags in feature files. To mention tags in feature files, use the following syntax:
For more information on custom fields, see this article.
If you use the Quantum feature to add Smart Reporting failure reasons from version 1.19, you will get the following error:
Ignoring Failure Reasons because JSON file was not found in the path
This error occurs due to a change in the structure of the JSON file introduced in version 1.20 to support custom fields and tags. For more information, read this article.