bahmutov / bahmutov/cypress-split
Need a better way of dealing with an empty list of specs
Open
enhancement
- Dominant language
- JavaScript
- Stars
- 285
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
Opened https://github.com/cypress-io/cypress/issues/25508
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the linked Cypress issue and then inspect how this repository handles an empty list of specs. Determine the expected behavior for parallel runs with no specs before identifying the relevant entry point and tests. Done means the behavior is documented by tests and the empty-spec case is handled consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cypress, javascript
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100