microsoft / microsoft/vscode-test-cli
Allow per-TestConfiguration ICoverageConfiguration
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 16
- Avg merge
- 10h 57m
- Merged PRs (30d)
- 2
Description
At the moment, coverage configuration (from ICoverageConfiguration) is defined globally:
export interface IConfigurationWithGlobalOptions {
/**
* Test configurations to run.
*/
tests: TestConfiguration[];
/**
* Configuration used for handling coverage.
*/
coverage?: ICoverageConfiguration;
}
This is unfortunately a bit limiting, as one cannot collect coverage separately, e.g., for integration vs. unit tests defined in two separate TestConfigurations. (Of course, this would also require that https://github.com/microsoft/vscode-test-cli/issues/38 be fixed; it both configurations write to the same output directory, this won't work.)
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 tracing IConfigurationWithGlobalOptions, its tests array, and the existing ICoverageConfiguration handling. Determine how coverage can be associated with each TestConfiguration, while reviewing issue #38 because shared output directories currently block separate collection. Done means per-test coverage configuration is supported without relying on one global coverage setting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100