Apologies if I’m not using the Categories/Tags correctly.
Had a weird experience with the rna-transcripton exercise in the Clojure track; it claimed that my solution both passed all tests and failed one test at the same time
I checked the test runner code and two other community solutions, and this issue seems to always be caused by an explicit assert that fails. If an AssertionError is thrown the other way, like so: (throw (AssertionError.)), everything works as it should.
However, there are two things worth noting:
Currently, this is the only exercise in the track that uses AssertionError in the tests, which allows people to use assert in their code and trigger this behavior.
The tests are out of sync with the problem specs, which don’t even include error checking. If we implement the new tests, this issue will no longer occur.
I believe Bobbi should immediately clarify what is going on.
In the meantime, I’ll create an issue on the clojure-test-runner repo and sync the tests.