The success of any Test Automation framework not only just depends on the way the framework is designed but also how effectively the reporting mechanism is implemented.
Test Automation report is the blueprint that shows how the script was executed, Steps involved, execution time and checkpoints that were passed or failed.
We have already seen so many reporting tools in the market such as Allure, Extent, TestNG, and so on. But in this article, I am going to walk you through the new reporting tool called ‘Tesults’.
Tesults is a web-based reporting and monitoring application for the automated test results and build status. Unlike Allure and Extent Report, there is nothing to set up in terms of infrastructure or software, but it requires you to sign-up, and You’re good to go!
They provide 2 plans to get you started with:
Free Tier: This plan helps you to create a project and access it as long as you want, but it comes with some limitation where you can have only 1 Target and a project can be accessed by 5 team members and a maximum of 100 test cases for each test run.
Tesults Plan: This is a paid plan which allows you to choose any number of Target (each target -> $25) and also comes with a default team size of 25 members and provides a maximum of 10,000 test cases for each test run.
Note: Target in simple terms is the environment on which you want to run your tests.
For some open-source projects or small teams who are getting started, they provide discounted or even free accounts if requested by mail, So teams who don't have a budget can also advantage of Tesults.
There are many features provided by Tesults:
- Support many test automation frameworks and languages: It supports many test automation frameworks with almost no code or very minimal code to integrate with other test frameworks and also provides various libraries to integrate various languages.
- Supports multiple ways to view result: Tesults provides a detailed and graphical analysis of your Test runs by providing different views.
Result View: The Result view displays all the test cases that are executed in that specific test run of all test suites, From here we can drill down and click specific test having information like test description, failure reason, parameters, test history and the associated files including logs and screen captures and any other data your tests collect.
Supplemental View: The supplemental view give information about new passes and continuos test failures in graphical format, which helps us to analyze the history of the test runs and know the health of our Test automation report.
Status View: Status view gives a high-level overview of the selected target and is mainly useful if you have many targets(test jobs), It shows the latest results from the entire project and one high-level view to find out if there are any specific areas that need attention.
Test-Case Detail: In the result-view, you can click on any test case to see the detailed information, which includes Test Name, description, Result, Params, Failure reason, Files section where we can attach the failed test case screenshot, Associated bug, Task, History, Comments by looking at all these information we can get complete information about result of test.
- Historical test analysis: Tesults allows you to view the historical test runs and automatically identify the flaky behavior of the test based on history.
- Hosted on the cloud: Tesults is a cloud-hosted application which means our test results are going to be available on a remote server and can be accessed at any time, The Only thing that is required is to sign-in, This feature makes Tesults unique from other test reporting tools.
- Flaky test indicator: Tesults intelligently identify tests that exhibit intermittent or sporadic behavior and add a ‘flaky’ icon to the test case that looks like it has changed the result between pass and fail few times.
- Bug linking: If the automation script fails because of some bug in the application then we can create a JIRA ticket and attach the link here by tagging the associated developer so that he can look into the issue and fix it, update it as fixed once the issue is resolved.
So in this article, we saw what is the importance of reporting in the Test Automation framework and explored a new reporting tool called ‘Tesults’ and various features it provides.
In the next part, we are going to see:
- Creation of a project in ‘Tesults’
- Integrate ‘Tesults’ with our current test automation framework which is built using Selenium as a UI automation tool, TestNG as a unit testing framework, and Gradle as a build tool.
- Update the test results in ‘Tesults’.
First, do it, then do it right, then do it better.