(<(counte)(counta))"actual is larger than expected"
(>(counte)(counta))"expected is larger than actual"))))
;; # ------------------------------ FUNCTIONS THAT GET RUN ON TEST SUITE START / STOP ------------------------------
;; `test-startup` function won't work for loading the drivers because they need to be available at evaluation time for some of the unit tests work work properly
;;; ------------------------------- Functions That Get Ran On Test Suite Start / Stop --------------------------------
;; `test-startup` function won't work for loading the drivers because they need to be available at evaluation time for
;; some of the unit tests work work properly
(driver/find-and-load-drivers!)
(defntest-startup
{:expectations-options:before-run}
[]
;; We can shave about a second from unit test launch time by doing the various setup stages in on different threads
;; Start Jetty in the BG so if test setup fails we have an easier time debugging it -- it's trickier to debug things on a BG thread
;; Start Jetty in the BG so if test setup fails we have an easier time debugging it -- it's trickier to debug things
;; on a BG thread
(let[start-jetty!(future(core/start-jetty!))]
(try
...
...
@@ -79,8 +82,8 @@
(setting/set!:site-name"Metabase Test")
(init-status/set-complete!)
;; make sure the driver test extensions are loaded before running the tests. :reload them because otherwise we get wacky 'method in protocol not implemented' errors
;; when running tests against an individual namespace
;; make sure the driver test extensions are loaded before running the tests. :reload them because otherwise we
;; get wacky 'method in protocol not implemented' errors when running tests against an individual namespace