Discussion on automation
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 564
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 10
Description
@leobalter and I have been chatting about automation. For the website, I need some metadata across all proposals and test262. This will require some maintenance from everyone in committee.
On the side of test262 -- I would need a way to verify which proposal a given issue or pr is addressing. This can be as simple as a link.
On the other hand, there might be space for even more automation here. Leo and I brainstormed a bit on the following:
- autogenerating a test plan from code coverage (we could use engine262 as a base)
- generating test cases automatically
- generating comments automatically
this would be a bigger intervention than I thought initially. What do people here think? Can we lighten the maintainer burden here?
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 test262 and website metadata needs, including how a proposal should be linked to an issue or pull request. Then compare the suggested engine262-based test-plan generation, automatic test cases, and automatic comments; done requires an agreed scope and maintainer-approved automation plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100