Tests that fail because they throw error don't report with a ❌
Open
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 301
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
When a test fails because it throws, it seems that it's reported differently:
(rcf/tests
(throw (ex-info "" {}))
:= 10)
Will report:
ERROR in () (:)
expected: (hyperfiddle.rcf/= (throw (ex-info "" {})) 10)
actual: clojure.lang.ExceptionInfo:
{}
at ...
Where-as:
(rcf/tests
20
:= 10)
Will report:
❌ FAIL in () (...:460)
expected: (= 20 10)
actual: (not (= 20 10))
I don't mind that it says ERROR instead of FAIL, but it be nice to still have a big red ❌
Contributor guide
No contributing guide indexed for this repository
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
Start by reproducing the two rcf/tests examples in the issue and compare their reported output. Trace the reporting path for the thrown ex-info case; done means that error reports still show ERROR if desired but include the large red ❌ indicator like ordinary failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100