Should we include more dependencies to TestModule.<Framework>Module
#3281
lefou
started this conversation in
Development
Replies: 1 comment 1 reply
-
For the Java mill/scalalib/src/mill/scalalib/TestModule.scala Lines 243 to 272 in 7147d76 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We currently don't add the dependencies to a concrete test runner in our
TestModule
traits.That means, users need to remember to add the correct dependencies themselves.
The reasons are twofold.
This lightweight approach is a bit inconvenient, since you need to look up the correct dependencies every time.
What about adding the dependencies, such that just adding a
extends TestModule.Utest
is enough to run a test? To keep version-update induced maintenance low, we could:Introduce a dedicated
version
target. Either a specific (TestModule.Utest.utestVersion
,TestModule.ZioTest.zioTestVersion
) or some generic (TestModule.Utest.testFrameworkVersion
).Introduce additional targets, to select a specific set of features and deduce the respective needed dependencies from it. (
TestModule.ScalaTest.suiteStyles: T[Seq[SuiteStyle]]
. E.g. to selectfree
we addscalatest-freespec
dependency)It would be also an opportunity to abstract over some framework specific settings like parallel running of suites/test or failure reporting.
Beta Was this translation helpful? Give feedback.
All reactions