[MGNLTEST-280] (Consider) proper cucumber scenario testing reporting Created: 27/Jun/22 Updated: 26/Oct/22 Resolved: 17/Oct/22 |
|
| Status: | Closed |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.4.0 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Epic Link: | cucumber-and-selenide-support-by-test-fwk | ||||||||
| Description |
|
Cucumber provides various possibilities to create test-reports. h4. MinimalEnsure we have proper reports in the jenkins log MoreCreate some "extra" reports |
| Comments |
| Comment by Christoph Meier [ 17/Oct/22 ] |
|
We are nearly there - what is missing will be tackled by Hence closing this one |