Add coverage functionality to stripes-testing method
Description
Environment
None
Potential Workaround
None
blocks
is blocked by
relates to
Checklist
hideTestRail: Results
Activity
Show:
Matt Jones January 9, 2019 at 3:26 PM
the issue is FOLIO-1664, now linked
Jakub Skoczen January 9, 2019 at 2:43 PM
can you please find the issue about problems with multiple nightmare instances and link it here as a blocker?
Matt Jones December 6, 2018 at 7:57 PM
, Keep in mind coverage at this stage would reflect the cross-module tests that reside within platform-core. Updates are still needed for the ui-modules linked to FOLIO-1618.
That said, ui-users has already been updated, so its coverage as reported through platform-core should reflect both the Nightmare tests within ui-users itself (as we saw running in isolation) and those tests from platform-core that interact with ui-users.
Anton Emelianov December 6, 2018 at 7:35 PM
, Could you please share coverage numbers if you have them?
Eric Valuk December 6, 2018 at 5:47 PM
Made a PR for to enable platform coverage: https://github.com/folio-org/platform-core/pull/106
Won't Do
Details
Details
Assignee
Eric ValukReporter
Eric ValukPriority
P3Development Team
Core: Platform
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created July 17, 2018 at 1:48 PM
Updated October 22, 2020 at 8:34 PM
Resolved October 22, 2020 at 8:34 PM
TestRail: Cases
TestRail: Runs
this will require wrapping current tests inside another mocha describe and then capturing all coverage in an after function. All tests will need to take a nightmare instance created one time so that we can capture all coverage and will not be able to call end(). These requirements are such that the entire test can be run then captured. Otherwise coverage will not be produced.