esid in tests of Stage 3 features
Open
Nobody has claimed this yet.
question
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 564
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 10
Description
I've seen a bunch of code go in with esid: pending when it's for a feature that hasn't landed yet, and I'm copying this in my PRs for other specs. Is this what we should be doing, or should we expect that the ids on pending specs are stable and just reference them?
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
Review the existing Stage 3 feature tests and their esid metadata, then compare how pending specs reference feature identifiers. Determine whether pending IDs should remain stable or use esid: pending, and document the agreed convention; the issue is complete when the project’s expected practice is explicit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100