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

Generate Code coverage reports to track our increasing testing coverage #8771

Closed
ghernandez345 opened this issue Nov 21, 2022 · 2 comments
Closed
Assignees
Labels
~engineering-initiated Engineering-initiated story, such as a bug, refactor, or contributor experience improvement. ~frontend Frontend-related issue. #g-mdm MDM product group :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. story A user story defining an entire feature
Milestone

Comments

@ghernandez345
Copy link
Contributor

ghernandez345 commented Nov 21, 2022

User Story

As an engineer, I need to be able to report on code quality KPIs so that the broader organization knows how we're doing.

Notes

We'd like to be able to measure our code coverage on Frontend to make sure we have a good amount of code tested. We can use the Jest coverage tooling to generate these reports

Requirements

  1. Create a mechanism to generate code coverage reports
  2. Add report to the github actions CI artefacts
  3. Documentation on use generation of coverage reports and their use.
@ghernandez345 ghernandez345 added story A user story defining an entire feature ~frontend Frontend-related issue. labels Nov 21, 2022
@ghernandez345 ghernandez345 removed the story A user story defining an entire feature label Nov 21, 2022
@ghernandez345 ghernandez345 added the :product Product Design department (shows up on 🦢 Drafting board) label May 22, 2023
@georgekarrv georgekarrv added ~engineering-initiated Engineering-initiated story, such as a bug, refactor, or contributor experience improvement. #g-mdm MDM product group :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. and removed :product Product Design department (shows up on 🦢 Drafting board) labels May 22, 2023
@ghernandez345 ghernandez345 self-assigned this May 23, 2023
@lukeheath lukeheath added the story A user story defining an entire feature label May 30, 2023
@lukeheath
Copy link
Member

lukeheath commented May 30, 2023

@ghernandez345 Since every ticket is either a story, bug, or ~sub-task, we will treat engineering initiatives as user stories. That means we'll create an issue with the User Story template and take it through the product drafting process.

I'm working on getting this handbooked; I know it's a bit confusing right now.

ghernandez345 added a commit that referenced this issue Jun 1, 2023
relates to #8771

Add coverage for frontend and improve coverage reports around Backend
and frontend code.
@lukeheath lukeheath added this to the 4.33.0 milestone Jun 13, 2023
@lukeheath lukeheath added :product Product Design department (shows up on 🦢 Drafting board) :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. and removed :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. :product Product Design department (shows up on 🦢 Drafting board) labels Jun 13, 2023
@fleet-release
Copy link
Contributor

Code coverage blooms,
Through the cloud's glass city,
Fleet's trust grows anew.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
~engineering-initiated Engineering-initiated story, such as a bug, refactor, or contributor experience improvement. ~frontend Frontend-related issue. #g-mdm MDM product group :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. story A user story defining an entire feature
Development

No branches or pull requests

4 participants