Skip to content

Commit d1f3dd9

Browse files
committed
docs: offer advice on installing test dependencies
Basically, acknowledge the need for dependencies and link to Fedora specfile which is the only sane place to find such a list. Closes: #16365 Signed-off-by: Ed Santiago <[email protected]>
1 parent 38ffed6 commit d1f3dd9

File tree

2 files changed

+6
-2
lines changed

2 files changed

+6
-2
lines changed

CONTRIBUTING.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -351,7 +351,7 @@ $ podman run -it --rm -e EPOCH_TEST_COMMIT -v $PWD:/usr/src/libpod:ro \
351351
validate
352352
```
353353

354-
### Integration Tests
354+
### Integration and Other Tests
355355

356356
Our primary means of performing integration testing for Podman is with the
357357
[Ginkgo](https://github.com/onsi/ginkgo) BDD testing framework. This allows
@@ -360,7 +360,7 @@ between Ginkgo and the Go test framework. Adequate test cases are expected to
360360
be provided with PRs.
361361

362362
For details on how to run the tests for Podman in your test environment, see the
363-
Integration Tests [README.md](test/README.md).
363+
testing [README.md](test/README.md).
364364

365365
## Continuous Integration
366366

test/README.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -133,6 +133,10 @@ Make sure that `bats` binary (`bin/bats` in the repository) is in your `PATH`, i
133133
PATH=$PATH:~/tools/bats/bin
134134
```
135135

136+
System tests also rely on `jq`, `socat`, `nmap`, and other tools. For a
137+
comprehensive list, see the `%package tests` section in the
138+
[fedora specfile](https://src.fedoraproject.org/rpms/podman/blob/main/f/podman.spec).
139+
136140
## Running system tests
137141
When `bats` is installed and is in your `PATH`, you can run the test suite with following command:
138142

0 commit comments

Comments
 (0)