cljs.test is part of core now so we should support it. There is a neat solution here for running the tests after each recompile using phantomjs, which I think is a good idea:
I think cljsbuild-ui should display this, not through the :notify-command config as shown above, but by parsing cljsbuild's :test-commands so the user can setup different tests, which they can enable from the UI like they enable builds. Running the tests should be done after each recompile as well.
oakmac
commented
9 years ago
cljs.testis part of core now so we should support it. There is a neat solution here for running the tests after each recompile using phantomjs, which I think is a good idea:I think cljsbuild-ui should display this, not through the
:notify-commandconfig as shown above, but by parsing cljsbuild's:test-commandsso the user can setup different tests, which they can enable from the UI like they enable builds. Running the tests should be done after each recompile as well.