rcf/set-timeout! incompatible with clojure.test which doesn't guarantee test order
Open
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 301
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
I have some tests where I need to set a specific timeout, say to assert that something does timeout. But it seems when we run tests through CI, I can't control what timeout set for which tests.
Normally I do:
(do
(rcf/set-timeout! 200)
(tests "That it times out"
...))
But like I said, I feel this doesn't generate a deftest that will execute with a 200ms timeout always.
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 from rcf/set-timeout! and reproduce the behavior through clojure.test, where test order is not guaranteed. Done means each generated test that sets a timeout consistently uses its intended timeout regardless of execution order, with a regression test covering the CI-like ordering.
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
- 35/100