@@ -10,43 +10,43 @@ MUnit, being a testing framework, is only available in test files: files in a `t
10
10
11
11
Alternatively, you can require just a specific version of MUnit:
12
12
``` scala
13
- //> using dep org.scalameta::munit:1.0.3
13
+ //> using dep org.scalameta::munit:1.1.0
14
14
```
15
15
{% endtab %}
16
16
{% tab 'sbt' %}
17
17
In your build.sbt file, you can add the dependency on toolkit-test:
18
18
``` scala
19
19
lazy val example = project.in(file(" ." ))
20
20
.settings(
21
- scalaVersion := " 3.3.4 " ,
22
- libraryDependencies += " org.scala-lang" %% " toolkit-test" % " 0.1.7 " % Test
21
+ scalaVersion := " 3.4.2 " ,
22
+ libraryDependencies += " org.scala-lang" %% " toolkit-test" % " 0.7.0 " % Test
23
23
)
24
24
```
25
25
26
26
Here the ` Test ` configuration means that the dependency is only used by the source files in ` src/test ` .
27
27
28
28
Alternatively, you can require just a specific version of MUnit:
29
29
``` scala
30
- libraryDependencies += " org.scalameta" %% " munit" % " 1.0.3 " % Test
30
+ libraryDependencies += " org.scalameta" %% " munit" % " 1.1.0 " % Test
31
31
```
32
32
{% endtab %}
33
33
{% tab 'Mill' %}
34
34
In your build.sc file, you can add a ` test ` object extending ` Tests ` and ` TestModule.Munit ` :
35
35
``` scala
36
36
object example extends ScalaModule {
37
- def scalaVersion = " 3.3.4 "
37
+ def scalaVersion = " 3.4.2 "
38
38
object test extends Tests with TestModule .Munit {
39
39
def ivyDeps =
40
40
Agg (
41
- ivy " org.scala-lang::toolkit-test:0.1.7 "
41
+ ivy " org.scala-lang::toolkit-test:0.7.0 "
42
42
)
43
43
}
44
44
}
45
45
```
46
46
47
47
Alternatively, you can require just a specific version of MUnit:
48
48
``` scala
49
- ivy " org.scalameta::munit:1.0.3 "
49
+ ivy " org.scalameta::munit:1.1.0 "
50
50
```
51
51
{% endtab %}
52
52
{% endtabs %}
0 commit comments