microsoft / microsoft/tolerant-php-parser
Add comprehensive set of tests for API
Open
Nobody has claimed this yet.
api
continuous-improvement
- Dominant language
- PHP
- Stars
- 894
- Forks
- 85
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
The API was somewhat haphazardly strewn together as an exploratory proof-of-concept, so it'll be good to start being more deliberate and increasing our test coverage in this area.
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 locating the API entry points and any existing test conventions in the repository. Review the current API behavior and identify gaps that the exploratory implementation leaves uncovered. Done means a comprehensive, deliberate test set covers the API, but the issue does not name specific files, cases, or acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100