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.

Sign up for GitHub

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

Jump to bottom

[Cypress] Code Coverage Report #2189

Open
Michaeldremy opened this issue May 10, 2024 · 1 comment
Open

[Cypress] Code Coverage Report #2189

Michaeldremy opened this issue May 10, 2024 · 1 comment
Assignees
@ojbravo @Michaeldremy

Comments

@Michaeldremy
Copy link
Contributor

Michaeldremy commented May 10, 2024 •
edited

Work to implement Code Coverage reports from Cypress to run frequently.
@Michaeldremy Michaeldremy created this issue from a note in Sprint 145 FE (To do) May 10, 2024
@Michaeldremy Michaeldremy moved this from To do to In progress in Sprint 145 FE May 10, 2024
@Michaeldremy Michaeldremy added this to In progress in Sprint 144 FE May 16, 2024
@Michaeldremy Michaeldremy removed this from In progress in Sprint 144 FE May 16, 2024
@ojbravo ojbravo added this to In progress in Sprint 146 FE May 22, 2024
@ojbravo ojbravo removed this from In progress in Sprint 145 FE May 22, 2024
@Michaeldremy Michaeldremy removed this from In progress in Sprint 146 FE Jun 20, 2024
@Michaeldremy
Copy link
Contributor Author

Code to run these reports is on a branch called 2189-code-cov-report. The numbers generated for the reports are taking into account Component Testing. At the current moment we have not implemented any component testing into the frontend, we only have end to end tests running.

Action Items:

  • Look into implementing Component Testing to improve numbers
    • Additionally removing certain files can help with increasing numbers as well
  • How to implement weekly code coverage report generation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ojbravo ojbravo

@Michaeldremy Michaeldremy

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ojbravo @Michaeldremy