Skip to content

SR-3237: Document libdispatch testsuite #190

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, 2017
Merged
Show file tree
Hide file tree
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
4 changes: 4 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,3 +18,7 @@ We are currently early in the development of this project. We began with a mirro
## Build and Install

For detailed instructions on building and installing libdispatch, see [INSTALL.md](INSTALL.md)

## Testing

For detailed instructions on testing libdispatch, see [TESTING.md](TESTING.md)
27 changes: 27 additions & 0 deletions TESTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
## Testing libdispatch

### Running tests

A C-based test suite can be found in the tests subdirectory.
It uses the automake testing harness to execute the tests.

A default set of tests that are always expected to pass can
be executed by doing

```
make check
```

An extended test suite that includes some tests that may fail
occasionally can be enabled at configure time:

```
./configure --enable-extended-test-suite
make check
```

### Additional prerequisites

A few test cases require additional packages to be installed.
In particular, several IO tests assume /usr/bin/vi is available
as an input file and will fail if it is not present.