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

Baseline test coverage for each repo #219

Open
2 tasks
Ben-Hodgkiss opened this issue Jan 13, 2025 · 0 comments
Open
2 tasks

Baseline test coverage for each repo #219

Ben-Hodgkiss opened this issue Jan 13, 2025 · 0 comments
Assignees

Comments

@Ben-Hodgkiss
Copy link
Contributor

Overview
We need to determine the test coverage on each repo so we know where coverage should be increased. The Providers team have already implemented this for the Submit repo using Vitest Coverage Report. We should investigate putting these on all relevant repos so we can baseline the test coverage.

Where test coverage < 80%, we should create a ticket per repo that is a sub-task of the Initiative ticket (#218) for the Live Service Team to work on over the quarter.

  • *By relevant, I think we mean any repos that are currently used - i.e. we can ignore the collection specific repos which are now centralised in Airflow.

Tech Approach
A bullet pointed list with details on how this could be technically worked.

  • Include links to relevant webpages, github files, user guides etc...
  • Person raising the ticket to have a first pass at this (if they know the approach) - Owen will then review and bring to refinement session.

Acceptance Criteria/Tests

  • We know the test coverage of each relevant repo in our Github organisation
  • Tickets have been created to increase the test coverage for any repos that are < 80%.
@Ben-Hodgkiss Ben-Hodgkiss moved this from Backlog to Refine, Prioritise & Plan in Infrastructure Jan 13, 2025
@Ben-Hodgkiss Ben-Hodgkiss moved this from Refine, Prioritise & Plan to Sprint Backlog in Infrastructure Jan 15, 2025
@cjohns-scottlogic cjohns-scottlogic moved this from Sprint Backlog to In Development in Infrastructure Jan 17, 2025
@cjohns-scottlogic cjohns-scottlogic self-assigned this Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Development
Development

No branches or pull requests

2 participants