Why kaocha dynamically add test files into classpath?

darkleaf · August 3, 2019, 7:53pm

lambdaisland/kaocha/blob/69cb244b62429749502d89c2087aa0ec0f87345e/src/kaocha/testable.clj#L74


(defn load
  "Given a testable, load the specified tests, producing a test-plan.


  Also performs validation, and lazy loading of the testable type's
  implementation."
  [testable]
  (load-type+validate testable)
  (doseq [path (:kaocha/test-paths testable)]
    (when-not (.exists (io/file path))
      (output/warn "In :test-paths, no such file or directory: " path))
    (classpath/add-classpath path))


  (try
    (-load testable)
    (catch Exception t
      (if (hierarchy/suite? testable)
        (assoc testable ::load-error t)
        (throw t)))))


(s/fdef load
  :args (s/cat :testable :kaocha/testable)

plexus · August 6, 2019, 8:00am

Hi @darkleaf,

This is mainly so you only have to declare your test directories in one place. Kaocha needs to know your test directories in order to watch files for changes, or to do code coverage analysis. This way you don’t have to repeat that information in two places.

It’s also so that if you have multiple non-overlapping test suites, we only add the directories that are needed to the class path.