microsoft / microsoft/vscode-cpptools
Build automation/tooling to support performance testing and monitoring of the extension
Open
Nobody has claimed this yet.
internal
Language Service
performance
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Feature Request
In order to do in-depth performance testing and monitoring of the cpptools extension we need to build some cross-plat automation and tooling to bring the data together
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 no files, tests, or entry points. Start by surveying the cpptools extension's existing performance-testing and monitoring setup, then identify the cross-platform automation and data-collection requirements. Done means tooling exists to run the performance work across platforms and bring its data together.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- performance, testing, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100