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

Include code coverage in continuous integration #4559

Open
rikurauhala opened this issue Jun 27, 2024 · 0 comments
Open

Include code coverage in continuous integration #4559

rikurauhala opened this issue Jun 27, 2024 · 0 comments
Labels
difficult to implement Lots of tunkkaus needed github actions GitHub Actions tests Test automation

Comments

@rikurauhala
Copy link
Contributor

rikurauhala commented Jun 27, 2024

Code coverage has been set up for our end-to-end tests. However, the report is not very useful if it can only be generated locally which takes a lot of time and maintains no history of the progress.

The coverage should be calculated and a report for it generated with GitHub Actions. The report should be pushed to Codecov.

Also pushing the coverage to Code Climate would be a nice addition but the actual UI/UX is much worse than with Codecov.

There is probably no need to include the coverage report in our current workflows. There could be a new separate workflow that runs at regular intervals, say once a day or once a week.

Steps to generate the report:

  • Instrument the code: npm run instrument
  • Run Oodikone with the instrumented code: npm run oodikone:test
  • Run tests in the terminal: npm run cypress run -- --browser chrome
  • View the report: firefox coverage/lcov-report/index.html

UPDATE: This has probably changed after the introduction of TypeScript to Oodikone.

@rikurauhala rikurauhala added tests Test automation github actions GitHub Actions difficult to implement Lots of tunkkaus needed labels Jun 27, 2024
@github-project-automation github-project-automation bot moved this to To do in Oodikone Jun 27, 2024
@rikurauhala rikurauhala moved this from To do to Next in Oodikone Jun 27, 2024
@rikurauhala rikurauhala moved this from Next to To do in Oodikone Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficult to implement Lots of tunkkaus needed github actions GitHub Actions tests Test automation
Projects
Status: To do
Development

No branches or pull requests

1 participant