Some tests are not being executed

[KuceraMartin]

Problem:
On the latest master, when I run ./mill 'build-module.test' 'scala.build.options.*', I would expect the ConfigMonoidTest to be executed but it is not.

Solution:
Either move ConfigMonoidTest from modules/options/src/test/scala/scala/build/options to modules/build/src/test/scala/scala/build/options, or setup tests so that files in the former directory will also get executed. (I am not sure which is the preferred option)

[lwronski]

Hi @KuceraMartin, thanks for reporting. To run unit tests for the options module, run the following command:

./mill 'options.test' 'scala.build.options.*'

To run unit tests for a different module, set module_name to the module name:

./mill '{module_name}.test' '*'

[KuceraMartin]

@lwronski Thanks for the explanation and for updating the docs.

Unfortunately, it seems to me that the tests are also not getting executed when running ./mill -i unitTests which is how unit tests are run here on the CI. In #1963 I intentionally tried to leave one failing test and even on the CI it only started failing after I moved the file to the build module.

I think it would be good to either fix this on the CI or to move the ConfigMonoidTest to the build module.

[lwronski]

Unfortunately, it seems to me that the tests are also not getting executed when running ./mill -i unitTests which is how unit tests are run here on the CI. In #1963 I intentionally tried to leave one failing test and even on the CI it only started failing after I moved the file to the build module.

Yes, you are right - good catch! I will reopen this issue