parse-community / parse-community/parse-server
Add CI check for test duration impact
Open
Nobody has claimed this yet.
type:meta
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
Currently, a PR may add poorly written tests that prolong the CI test duration, for example by reconfiguring the server unnecessarily often or using async timeout.
Feature / Enhancement Description
Add CI check to evaluate test duration impact.
Example Use Case
n/a
Alternatives / Workarounds
Manual observation.
3rd Party References
n/a
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 repository's CI workflows and test commands first, then determine how current test duration is measured for pull requests. Done means a CI check identifies a meaningful duration increase caused by test changes and reports the result clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100