@@ -17,7 +17,7 @@ The entire suite of tests can be run using the bootstrapped compiler as follows:
1717
1818``` bash
1919$ sbt
20- > dotty -bootstrapped/test
20+ > scala3 -bootstrapped/test
2121```
2222
2323There 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:
3232
3333``` bash
3434$ sbt
35- > dotty -compiler/test
35+ > scala3 -compiler/test
3636```
3737
3838To run a single test class you use ` testOnly ` and the fully qualified class name.
@@ -130,7 +130,7 @@ $ sbt
130130### Bootstrapped-only tests
131131
132132To 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).
134134Some tests can only be run in bootstrapped compilers; that includes all tests
135135with ` with-compiler ` in their name.
136136
@@ -144,10 +144,15 @@ with `with-compiler` in their name.
144144 > testCompilation --from-tasty
145145 ```
146146
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.
148148
149149### SemanticDB tests
150150
151+ ``` bash
152+ $ sbt
153+ > scala3-compiler-bootstrapped/testOnly dotty.tools.dotc.semanticdb.SemanticdbTests
154+ ```
155+
151156The output of the ` extractSemanticDB ` phase, enabled with ` -Xsemanticdb ` is tested with the bootstrapped JUnit test
152157` dotty.tools.dotc.semanticdb.SemanticdbTests ` . It uses source files in ` tests/semanticdb/expect ` to generate
153158two 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.
157162
158163The test suite will create a new file if it detects any difference, which can be compared with the
159164original 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
161166control.
0 commit comments