[FOLIO-1664] figure out what goes wrong when passing a single Nightmare instance Created: 19/Dec/18 Updated: 12/Jun/20 Resolved: 12/Jun/20 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P3 |
| Reporter: | Jakub Skoczen | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | sprint53, sprint54 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||
| Sprint: | |||||||||||||||||||||
| Description |
|
Zak Burke Matthew Jones Eric Valuk Guys, please provide more information here. |
| Comments |
| Comment by Eric Valuk [ 19/Dec/18 ] |
|
I can only comment on how it works currently, I dont have much info on how it breaks at the moment. Previously each test was creating a Nightmare object internally which was ended after each test sequence. In order to direct the nightmare instance and collect coverage information from the object after the tests were complete the nightmare object is now created once and passed through to each test to run its respective cases. At the end of the tests the coverage data is saved out to disk where it is then used to generate the report. Possible theories about issues(complete guesses): 1) Nightmare state could now be messy between test cases and require clean up |
| Comment by Matthew Jones [ 09/Jan/19 ] |
|
Related PRs disabling use of the shared Nightmare instance for reference: |
| Comment by Jakub Skoczen [ 12/Jun/20 ] |
|
Closing as outdated. Re-open if needed. |