Skip to content

Update intructions to run a single test #2247

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.

Sign up for GitHub

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
Apr 13, 2017
Merged

Update intructions to run a single test #2247

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
7 changes: 3 additions & 4 deletions docs/docs/contributing/testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,10 +80,9 @@ This might be aliased in the future. It is also possible to run tests filtered
by using:

```bash
> filterTest .*i2147.scala
> vulpix i2147.scala
```

This will run both the test `./tests/pos/i2147.scala` and
`./tests/partest-test/i2147.scala` since both of these match the given regular
expression. This also means that you could run `filterTest .*` to run all
integration tests.
`./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.
15 changes: 5 additions & 10 deletions docs/docs/contributing/workflow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,20 +57,15 @@ $ sbt
To test a specific test tests/x/y.scala (for example tests/pos/t210.scala):

```bash
> filterTest .*pos/t210.scala
> vulpix pos/t210.scala
```

The filterTest task takes a regular expression as its argument. For example,
you could run a negative and a positive test with:
The `vulpix` task uses its argument for a substring test. For example, you
could run both a negative and a positive test with the same name
(`pos/i2101.scala` & `neg/i2101.scala`):

```bash
> filterTest (.*pos/t697.scala)|(.*neg/i2101.scala)
```

or if they have the same name, the equivalent can be achieved with:

```bash
> filterTest .*/i2101.scala
> vulpix i2101.scala
```

## Inspecting Trees with Type Stealer ##
Expand Down