-
Task
-
Resolution: Done
-
L3 - Default
-
None
Problem
- When the E2E job indicates a broken build because of failing test cafe tests, I cannot easily spot which tests are failing in the Jenkins UI
- It is super hard to spot the failing test cases just from looking at the enormous console output file
Solution
Configure a reporter [1] (probably xUnit) so that an XML report is written that can be consumed by Jenkins
Hints
- Besides changes in the test cafe configuration, the jenkins job configuration might change slightly
- For protractor, a report in the xUnit format is written
[1] https://devexpress.github.io/testcafe/documentation/using-testcafe/common-concepts/reporters.html
This is the controller panel for Smart Panels app
[CAM-10890] Configure test cafe reporter correctly
Assignee | Original: Thorben Lindhauer [ thorben.lindhauer ] | New: Martin Stamm [ martin.stamm ] |
Status | Original: Open [ 1 ] | New: Ready [ 10005 ] |
Status | Original: Ready [ 10005 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: Ready [ 10005 ] |
Status | Original: Ready [ 10005 ] | New: In Progress [ 3 ] |
Resolution | New: Done [ 10000 ] | |
Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
Remaining Estimate | New: 0 minutes [ 0 ] | |
Original Estimate | New: 0 minutes [ 0 ] |
Fix Version/s | New: 7.12.0-alpha5 [ 15544 ] |