Skip to content

Update documentation after #3665 #3677

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 4, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions docs/docs/contributing/testing.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,14 +24,14 @@ $ sbt
> dotty-compiler/test
```

To run a single test class you use `testOnly` and the fully qualified class name.
To run a single test class you use `testOnly` and the fully qualified class name.
For example:

```bash
> testOnly dotty.tools.dotc.transform.TreeTransformerTest
```

The test command follows a regular expression-based syntax `testOnly * -- *`.
The test command follows a regular expression-based syntax `testOnly * -- *`.
The right-hand side picks a range of names for methods and the left-hand side picks a range of class names and their
fully-qualified paths.

Expand All @@ -58,13 +58,13 @@ You can also run all paths of classes of a certain name:
These tests are Scala source files expected to compile with Dotty (pos tests),
along with their expected output (run tests) or errors (neg tests).

All of these tests are contained in the `./tests/*` directories and can be run with the `vulpix` command.
All of these tests are contained in the `./tests/*` directories and can be run with the `testCompilation` command.

Currently to run these tests you need to invoke from sbt:

```bash
$ sbt
> vulpix
> testCompilation
```

(which is effectively the same with `testOnly dotty.tools.dotc.CompilationTests`)
Expand All @@ -73,9 +73,9 @@ It is also possible to run tests filtered, again from sbt:

```bash
$ sbt
> vulpix i2147.scala
> testCompilation companions
```

This will run both the test `./tests/pos/i2147.scala` and
`./tests/partest-test/i2147.scala` since both of these match the given string.
This also means that you could run `vulpix` with no arguments to run all integration tests.
This will run both the test `./tests/pos/companions.scala` and
`./tests/neg/companions.scala` since both of these match the given string.
This also means that you could run `testCompilation` with no arguments to run all integration tests.