Skip to content

Commit

Permalink
Update readme.md
Browse files Browse the repository at this point in the history
  • Loading branch information
l-kent authored Sep 24, 2024
1 parent 3030d6b commit 4fb69f1
Showing 1 changed file with 16 additions and 8 deletions.
24 changes: 16 additions & 8 deletions docs/development/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -119,28 +119,36 @@ Full details can be found [here](../src/test/readme.md).

### Running Tests

The test suites use [ScalaTest](https://www.scalatest.org/), they can be run via.
The test suites use [ScalaTest](https://www.scalatest.org/).

To run the primary SystemTests suites (SystemTestsBAP and SystemTestsGTIRB) (which require Boogie):

```
$ mill test
$ mill.test.testOnly 'SystemTests*'
```

To run a single test suite, for example only the system tests (requires boogie):
To run a single test from a test suite, it can be selected using globbing on the full test class name with the `testOnly` task:

```
$ mill.test.testOnly SystemTests
$ mill test.testOnly 'SystemTestsBAP' -- -z basic_arrays_read/gcc:BAP
```

To run single tests in from the test suite, they can be selected using globbing on the full test class name with the `testOnly` task:
To update the expected BASIL output files from the SystemTests results run:

```
$ mill test.testOnly '*SystemTests*' -- -z basic_arrays_read -z basic_arrays_write
$ mill updateExpected
```

To update the expected basil output files from the test results run
To run another test suite, just use the name of the class containing the test suite (in this case LiveVarsAnalysisTests):

```
$ mill updateExpected
$ mill.test.testOnly 'LiveVarsAnalysisTests'
```

To list all test suites:

```
$ mill.test.testOnly * -- -t ''
```

## Performance profiling
Expand Down

0 comments on commit 4fb69f1

Please sign in to comment.