Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[USER-v2] Running code coverage on netlify build by a manual trigger #670

Open
elvijsTDL opened this issue Aug 31, 2023 · 0 comments
Open
Assignees
Labels
Type: Spike Task that is to be timeboxed

Comments

@elvijsTDL
Copy link
Contributor

Currently I am running code coverage by myself locally and although there are scripts for it , there are still some problems if someone else would like to run it and the process takes about 2-3 hours drastically slowing down the computer its ran on:

Stream details page redirects won't work in build mode so dev mode has to be used to have a smaller test run
Gnosis safe connection tests won't work because chromeWebSecurity has to be set to false for a specific test run
All of the networks will not be covered, because it would require to run the tests per network

To eleviate the pain it would be great to have a workflow which would:

— build app with shouldInstrumentCode enabled
— deploy instrumented build to netlify
— save in previous step output or get the url for the cypress tests to run on
— run the test cases we are usually running with some minimal changes to add the coverage
— rename and save code coverage report json artifact
— download all code coverage report jsons
— merge jsons together
— generate html nyc report
— save html folder as an artifact to download

Not 100% sure it would work on a deployed version, but a quick spike to see if its possible would be nice

@elvijsTDL elvijsTDL added the Type: Spike Task that is to be timeboxed label Aug 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Spike Task that is to be timeboxed
Projects
None yet
Development

No branches or pull requests

2 participants