Consider to run testrunner as a service and provide an API
Open
type-enhancement
- Dominant language
- Dart
- Stars
- 536
- Forks
- 232
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 10
Description
- watch the test directory for changes
- provide a list of tests/groups found (maybe with additional changes, browser/command line, tags)
- allow to run a set of tests
- provide the test result (progress)
- allow to subscribe to updates (notification for new/modified/deleted tests)
This would allow to easily build a nice GUI or control it from an IDE
Contributor guide
Research direction
No files or tests are named. Start by mapping the existing Dart testrunner entry points and test-discovery flow, then define the service and API boundaries for watching changes, listing tests, running selections, reporting progress, and notifying subscribers. Done means these capabilities are specified well enough to support a GUI or IDE client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- api, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100