Problem Matcher for testing/CI
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5k
- Forks
- 1.7k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 2
Description
How can we enable problem matchers for various testing tools like https://github.com/mochajs/mocha? Is there a reporting format that we should use for it to be matched by the runner when errors occur in the test cases? I saw the problem matchers for eslint like estlint-stylish but didn't see anything else.
If anyone can point me in the right direction, I'm happy to create the matcher if it doesn't already exist.
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 reviewing GitHub Actions problem matcher documentation and the existing eslint-stylish matcher referenced in the issue. The issue names no repository files or tests, so first establish which testing tools and reporting format are in scope; done means an agreed matcher exists and its test-case errors are recognized by the runner.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, nodejs
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100