You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 28, 2019. It is now read-only.
Right now, the Clojure/Jaunt test suite does one round of clojure.test running which touches pretty much everything. It should be possible to refactor the test runner script to provide much better output, including per-test suite failures. In part this helps track the various parts of the Clojure/Jaunt codebase which literally have no tests.
This is likely to be a bit of an adventure, and may involve some classloader voodoo to create sandboxes during test loading and evaluation. I've tried to get this working a couple times before and found really interesting data dependency behavior between the test namespaces.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now, the Clojure/Jaunt test suite does one round of
clojure.test
running which touches pretty much everything. It should be possible to refactor the test runner script to provide much better output, including per-test suite failures. In part this helps track the various parts of the Clojure/Jaunt codebase which literally have no tests.This is likely to be a bit of an adventure, and may involve some classloader voodoo to create sandboxes during test loading and evaluation. I've tried to get this working a couple times before and found really interesting data dependency behavior between the test namespaces.
The text was updated successfully, but these errors were encountered: