@@ -17,7 +17,7 @@ The entire suite of tests can be run using the bootstrapped compiler as follows:
17
17
18
18
``` bash
19
19
$ sbt
20
- > dotty -bootstrapped/test
20
+ > scala3 -bootstrapped/test
21
21
```
22
22
23
23
There are currently several forms of tests in Dotty. These can be split into
@@ -32,7 +32,7 @@ To run all tests in e.g., for the compiler test-suite you can write:
32
32
33
33
``` bash
34
34
$ sbt
35
- > dotty -compiler/test
35
+ > scala3 -compiler/test
36
36
```
37
37
38
38
To run a single test class you use ` testOnly ` and the fully qualified class name.
@@ -130,7 +130,7 @@ $ sbt
130
130
### Bootstrapped-only tests
131
131
132
132
To run ` testCompilation ` on a bootstrapped Dotty compiler, use
133
- ` dotty -compiler-bootstrapped/testCompilation` (with the same syntax as above).
133
+ ` scala3 -compiler-bootstrapped/testCompilation` (with the same syntax as above).
134
134
Some tests can only be run in bootstrapped compilers; that includes all tests
135
135
with ` with-compiler ` in their name.
136
136
@@ -144,10 +144,15 @@ with `with-compiler` in their name.
144
144
> testCompilation --from-tasty
145
145
```
146
146
147
- This mode can be run under ` dotty -compiler-bootstrapped/testCompilation` to test on a bootstrapped Dotty compiler.
147
+ This mode can be run under ` scala3 -compiler-bootstrapped/testCompilation` to test on a bootstrapped Dotty compiler.
148
148
149
149
### SemanticDB tests
150
150
151
+ ``` bash
152
+ $ sbt
153
+ > scala3-compiler-bootstrapped/testOnly dotty.tools.dotc.semanticdb.SemanticdbTests
154
+ ```
155
+
151
156
The output of the ` extractSemanticDB ` phase, enabled with ` -Xsemanticdb ` is tested with the bootstrapped JUnit test
152
157
` dotty.tools.dotc.semanticdb.SemanticdbTests ` . It uses source files in ` tests/semanticdb/expect ` to generate
153
158
two kinds of output file that are compared with "expect files": placement of semanticdb symbol occurrences inline in
@@ -157,5 +162,5 @@ Expect files are used as regression tests to detect changes in the compiler.
157
162
158
163
The test suite will create a new file if it detects any difference, which can be compared with the
159
164
original expect file, or if the user wants to globally replace all expect files for semanticdb they can use
160
- ` dotty -compiler-bootstrapped/test:runMain dotty.tools.dotc.semanticdb.updateExpect` , and compare the changes via version
165
+ ` scala3 -compiler-bootstrapped/test:runMain dotty.tools.dotc.semanticdb.updateExpect` , and compare the changes via version
161
166
control.
0 commit comments