Batch-testing for specific errors
Open
testing-framework
- Dominant language
- Kotlin
- Stars
- 5
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Instead of only having "non-compiling" and "compiling" folders, we could have "flow-error" folder, "type-error" folders, and assert for specific errors
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not name files, tests, or entry points. Start by locating the existing "non-compiling" and "compiling" test folders, then determine how flow errors and type errors are currently classified and asserted. Done means the test organization supports those error categories and checks specific errors, but the desired error cases are not defined here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- compilers, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100