microsoft / microsoft/vscode-cmake-tools
[Feature] Break out LCOV test coverage into its own test configuration
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 546
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 32
Description
Request Overview
The LCOV tests add a requirement that LCOV be installed on the system. This is fine for the LCOV tests, but I don't like the dependency that it creates for all of the other single-root-UI tests.
I want to break it out into its own configuration so that I only have to install LCOV (or make local changes), if I want to test LCOV, which has the requirement of installing LCOV on the system.
Additional Information
No response
Contributor guide
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
The issue names the LCOV tests and the single-root-UI test configuration, but no files or entry points. Start by locating those test configurations and comparing their dependencies. Done means LCOV tests run in a separate configuration without making LCOV a requirement for other single-root-UI tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, typescript
- Domain
- build-system, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100