[FOLIO-1602] Enable coverage reporting on UI nightmare tests Created: 30/Oct/18 Updated: 22/Oct/20 Resolved: 22/Oct/20 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | ci, sprint50, sprint51, sprint52, sprint53, sprint54 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||
| Sprint: | |||||||||||||||||||||
| Development Team: | Core: Platform | ||||||||||||||||||||
| Description |
|
Enable code coverage reporting for nightmare-based UI tests. |
| Comments |
| Comment by John Malconian [ 30/Oct/18 ] |
|
Functionality which adds test coverage reporting for nightmare-based UI integration tests has recently been implemented in stripes-testing and is enabled by appending the '--coverage' option when tests are invoked via stripes-cli. Coverage reporting is currently only possible for individual module tests. However, these tests are currently disabled on a per repo basis. |