microsoft / microsoft/typescript-analyze-trace
Add baseline tests
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 429
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Matrix:
- file vs dir
- types (un)available
- source (un)available
- json vs text
It needs to be possible to diff against the old baseline and accept the new baseline.
The biggest obstacle is likely to be source file lookup - real traces use absolute paths, but those won't be portable (e.g. to CI machines). Post-processing the trace files (i.e. test cases) to use forward-slash-delimited relative paths might suffice.
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
Start by reviewing the existing trace files and any baseline comparison workflow, using the matrix of file-versus-directory, type and source availability, and JSON-versus-text cases. Define how old and new baselines are compared and accepted, then check whether converting absolute source paths to forward-slash relative paths keeps the cases portable in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100