Test coverage keeps slipping. What can you set up on GitHub?
Why C is the answer
An automation that checks weekly for missing tests and proposes additions
GitHub describes this exact pattern. An automation proposes additions, and people review them.
In detail
- An automation can check weekly for missing tests.
- It proposes additions, and people review them.
- Review proposals like any other code.
Use case
An illustrative scenario, not a real incident.
Coverage keeps slipping. A weekly automation checks for missing tests and proposes additions, and people review them.
See it in different ways
sequenceDiagram participant D as Developer participant A as Copilot cloud agent participant G as GitHub D->>A: Task A->>G: Opens a branch and pull request G-->>D: Asks for review D->>G: Approves or asks for changes
flowchart LR S0["Weekly run"] --> S1["Finds missing tests"] --> S2["Proposes additions"] --> S3["People review"]
Key point: Automate the check, and keep the review.
Why the other options are wrong
- A. A prompt file that developers are asked to read before each code review
- A prompt file does not check anything.
- B. A policy that disables Copilot for the developers with the lowest coverage
- Disabling Copilot does not add tests.
- D. A rule that deletes any function that does not have a test written for it
- Deleting code is destructive and unhelpful.