Feature request: run figwheel.main.generated.build-auto-test-runner

[timothypratley]

Figwheel provides excellent convenience with the :auto-testing flag. However, it is currently not possible to run the generated tests from the command line. This means that to have a CI job run tests, you must craft your own test runner. This in turn necessitates requiring all test namespaces or crafting a bespoke test runner generation. Figwheel already does a really good job of this and in addition, hooks the generation so that it can pick up new tests. So it would be preferable to simply use :auto-testing.

The blocker is that the namespace of the generated test runner: figwheel.main.generated.build-auto-test-runner does not exist initially, and is not on the classpath, and figwheel.main refuses to attempt to run it:

:main-opts   ["-m" "figwheel.main" "--compile-opts" "webapp.cljs.edn"
              "-fwo" "{:auto-testing true, :launch-js [\"/usr/bin/firefox\" \"--headless\" :open-url]}"
              "-m" "figwheel.main.generated.webapp-auto-test-runner"]

Fails with

Error in command line args
-- Spec failed --------------------

  ["--compile-opts"
   "webapp.cljs.edn"
   "-fwo"
   "{:auto-testing true, :launch-js [\"/usr/bin/firefox\" \"-headless\" :open-url]}"
   "-m"
   "figwheel.main.generated.webapp-auto-test-runner"]
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

should be a CLJS namespace available on the classpath

This is the classic chicken and egg dilemma!

Bypassing the spec check does not solve the problem, because :auto-testing only kicks in when you do a --build but not a -m.
I think it would be necessary to combine both --build-once and -m; However this is not currently possible because the only thing that can follow --build-once is --serve.

It feels like there is an opportunity here, but I'm out of ideas on how to both build :auto-testing and launch it from the command line.