You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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%.
The text was updated successfully, but these errors were encountered:
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.
Tech Approach
A bullet pointed list with details on how this could be technically worked.
Acceptance Criteria/Tests
The text was updated successfully, but these errors were encountered: