Currently lein-midje respects a given :test-path. For projects that have Java sources too, which also will be tested with Midje, it would be useful to be able to specify multiple test paths. This could happen via a new key/value pair in the project.clj file. I suggest not to overwrite the behaviour of the existing :test-path because that one gets exported into the pom.xml file. So something like :midje {:paths ["test/clj", "test/java"]} could solve this. If the value will be a map then that could be extended in the future for more Midje options.
Currently lein-midje respects a given
:test-path
. For projects that have Java sources too, which also will be tested with Midje, it would be useful to be able to specify multiple test paths. This could happen via a new key/value pair in the project.clj file. I suggest not to overwrite the behaviour of the existing:test-path
because that one gets exported into the pom.xml file. So something like:midje {:paths ["test/clj", "test/java"]}
could solve this. If the value will be a map then that could be extended in the future for more Midje options.