Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No test execution if :advanced and no runner out dir #30

Closed
mfikes opened this issue Jun 14, 2019 · 1 comment · Fixed by #31
Closed

No test execution if :advanced and no runner out dir #30

mfikes opened this issue Jun 14, 2019 · 1 comment · Fixed by #31

Comments

@mfikes
Copy link
Contributor

mfikes commented Jun 14, 2019

If you don't yet have a cljs-test-runner-out dir, and you run tests with :advanced, then no tests are run.

Repro:

test/foo/core_test.cljs:

(ns foo.core-test
  (:require [clojure.test :refer [deftest is]]))

(deftest sample-test
  (is (== 1 1)))

deps.edn:

{:deps {org.clojure/clojurescript {:mvn/version "1.10.520"}}
 :aliases {:test {:extra-deps  {olical/cljs-test-runner {:mvn/version "3.5.0"}}
                  :extra-paths ["test" "cljs-test-runner-out/gen"]
                  :main-opts   ["-m" "cljs-test-runner.main"]}}}

Then running the tests produces no output:

$ clojure -A:test -c '{:optimizations :advanced}'

Running them a second time will:

$ clojure -A:test -c '{:optimizations :advanced}'

Testing foo.core-test

Ran 1 tests containing 1 assertions.
0 failures, 0 errors.
@Olical
Copy link
Owner

Olical commented Jun 14, 2019

I'm afraid this is a known gotcha 😭 if you have any tips then I'd love to hear them!

mfikes added a commit to mfikes/cljs-test-runner that referenced this issue Jun 14, 2019
mfikes added a commit to mfikes/cljs-test-runner that referenced this issue Jun 14, 2019
mfikes added a commit to mfikes/cljs-test-runner that referenced this issue Jun 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants