microsoft / microsoft/go-sqlcmd
Protect source files already at 100% code coverage - add "100PercentClub" build pipeline check
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 595
- Forks
- 91
- Avg merge
- 9h 35m
- Merged PRs (30d)
- 1
Description
The modern CLI uses a dependency injection architecture which makes it easier for most source files to get to 100% unit test code coverage. To keep this 100% code coverage culture moving forward for new source files, it would be good to be able to annotate source files that have once hit 100% unit test coverage, to not be able to drop below 100% again (a build pipeline break will prevent PRs merging that regress a source file that has previously been at 100% code coverage)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the repository's build pipeline and unit-test coverage configuration; the issue does not name files, tests, or an entry point. Determine how source files would be annotated and how a regression below 100% would be detected and reported, then define the build check and its completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100