Bug 36797 - Invalid Jenkins-Format
Invalid Jenkins-Format
Status: RESOLVED WORKSFORME
Product: UCS@school
Classification: Unclassified
Component: ucs-test
unspecified
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS@school maintainers
:
Depends on: 34014
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-18 11:18 CET by Philipp Hahn
Modified: 2020-11-10 08:00 CET (History)
3 users (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:
best: Patch_Available+


Attachments
Fix UCS@School tests (9.16 KB, patch)
2014-11-18 11:18 CET, Philipp Hahn
Details | Diff
Fix UCS@School tests v2 (9.95 KB, patch)
2014-11-18 11:24 CET, Philipp Hahn
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2014-11-18 11:18:33 CET
Created attachment 6402 [details]
Fix UCS@School tests

+++ This bug was initially created as a clone of Bug #34014 +++

The generated JUnit XML Format is causing problems with Jenkins:
3. The class-name uses a file-name, where the section and test-case are separated by "/", while for Jenkins a dot (".") must be used. Because of that all tests are put in the "(root)" package and are not separated by sections.
Comment 1 Philipp Hahn univentionstaff 2014-11-18 11:24:07 CET
Created attachment 6403 [details]
Fix UCS@School tests v2
Comment 2 Stefan Gohmann univentionstaff 2016-01-20 12:39:23 CET
Move to UCS@school.
Comment 3 Philipp Hahn univentionstaff 2020-11-10 08:00:30 CET
Not reported again since 2014