You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I've taken a liking to a style of writing tests where you colocate your tests with the actual source code, i.e. you have your defns immediately followed by a corresponding deftest. This makes it very easy to see which parts of your project are unit tested, and the tests also document how the function is supposed to be called, and what is the expected return value. We sometimes have more extensive or verbose tests in the test/ folder, but colocated tests always test at least the "happy path".
Describe the solution you'd like
Currently the lein-polylith plugin's test command seems to collect all namespaces it finds from component's test/ folder, and runs those tests. I'm wondering if it would be better to always just respect the :test-paths value from project.clj, as this is something most Clojure developers are probably used to. Alternatively, if :test-paths is found, the tool could use that, or if :test-paths is not found, the test/ folder could be used as a fallback?
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I've taken a liking to a style of writing tests where you colocate your tests with the actual source code, i.e. you have your
defn
s immediately followed by a correspondingdeftest
. This makes it very easy to see which parts of your project are unit tested, and the tests also document how the function is supposed to be called, and what is the expected return value. We sometimes have more extensive or verbose tests in the test/ folder, but colocated tests always test at least the "happy path".Describe the solution you'd like
Currently the
lein-polylith
plugin's test command seems to collect all namespaces it finds from component's test/ folder, and runs those tests. I'm wondering if it would be better to always just respect the:test-paths
value fromproject.clj
, as this is something most Clojure developers are probably used to. Alternatively, if:test-paths
is found, the tool could use that, or if:test-paths
is not found, the test/ folder could be used as a fallback?The text was updated successfully, but these errors were encountered: