-
Planned
0
AI error analysis - give more comprehensive information about errors ...
The trend with AI being what it is, is ther a plan to implement in the error analysis on reports an AI analysis : - tell the user what went wrong, like "the object XXX ...by: Olivier B. | about a month ago | Last activity about a month ago | Status changed about a month ago | Analytics/Reports
-
Planned
0
Add in reports if the device encountered a network issue during a run
Add in the report if we have network errors during the run (like for example if an application tested uses a backend on the internet and we have an HTTP 500, 403 or 404 ...by: Olivier B. | about a month ago | Last activity about a month ago | Status changed about a month ago | Analytics/Reports
-
Planned
1
View reason for failure directly on the reports screen
This way users will not have to open the report to see what went wrong. Modify the Report screen to provide an analysis of what went wrong right on the report screen, in ...by: Olivier B. | about a month ago | Last activity about a month ago | Status changed about a month ago | Analytics/Reports
-
Planned
0
Reporting - Smart comparison between current run and a previous passed ...
To facilitate the analysis of issues encountered when running tests : Expand the rreporting to be able to compare current run with previous passed run and provide an ...by: Olivier B. | about a month ago | Last activity about a month ago | Status changed about a month ago | Analytics/Reports