-
Notifications
You must be signed in to change notification settings - Fork 632
Enforce 100% code coverage in all new code [Blocked: #1726, #1725, #1497] #1727
Copy link
Copy link
Open
Open
Copy link
Labels
Impact: LowLow perceived user impact (e.g. edge cases).Low perceived user impact (e.g. edge cases).Work: MediumThe means to find the solution is clear, but it isn't at good-first-issue level yet.The means to find the solution is clear, but it isn't at good-first-issue level yet.Z-ibtTemporary label for Ben to keep track of issues he's triaged.Temporary label for Ben to keep track of issues he's triaged.enhancementEnd user-perceivable enhancements.End user-perceivable enhancements.
Metadata
Metadata
Assignees
Labels
Impact: LowLow perceived user impact (e.g. edge cases).Low perceived user impact (e.g. edge cases).Work: MediumThe means to find the solution is clear, but it isn't at good-first-issue level yet.The means to find the solution is clear, but it isn't at good-first-issue level yet.Z-ibtTemporary label for Ben to keep track of issues he's triaged.Temporary label for Ben to keep track of issues he's triaged.enhancementEnd user-perceivable enhancements.End user-perceivable enhancements.
Type
Projects
Status
Todo
As a follow-up to #1726, once the codebase reaches 90% code coverage we should introduce a check requiring that all new code have 100% code coverage in an effort to move the codebase as a whole toward 100% code coverage.
Incidentally, this is also blocked on #1725 and #1497.
Note that this is considered part of shipping the app, but as a nice-to-have and not a hard blocker. Reaching 90% code coverage is the key impact that's important for the launch, and while we can live without this issue, it will help keep code coverage up leading into the launch itself.