Better error reporting: Page errors and per test timeouts
Open
- Dominant language
- JavaScript
- Stars
- 119
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Currently, the most common Testee error is test timeouts. This can happen for any reason. Some solutions for implementing better reporting:
- [ ] Report errors on the page (potentially with a global error handler) like syntax errors etc
- [ ] Implement a per-test timeout. Currently a timeout does not include if it timed out on a specific test.
Contributor guide
Research direction
Start by tracing the existing timeout handling and browser page error reporting paths, since the issue names no files or tests. Review how failures are currently surfaced, then verify that page errors are reported and that timeout messages identify the specific test that exceeded its limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100