diff options
author | gVisor bot <gvisor-bot@google.com> | 2020-05-26 17:39:19 -0700 |
---|---|---|
committer | gVisor bot <gvisor-bot@google.com> | 2020-05-26 17:40:57 -0700 |
commit | 92bafd79293b99aac0ddeada11dfbe1fd9b67f13 (patch) | |
tree | 5b85bc19bab4b6bffc41a3c60138200f814bad77 /test/packetimpact/README.md | |
parent | 6111950f896be20619e903aa556ed921938bef4b (diff) |
Automated rollback of changelist 311424257
PiperOrigin-RevId: 313300554
Diffstat (limited to 'test/packetimpact/README.md')
-rw-r--r-- | test/packetimpact/README.md | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/test/packetimpact/README.md b/test/packetimpact/README.md index a82ad996a..f46c67a0c 100644 --- a/test/packetimpact/README.md +++ b/test/packetimpact/README.md @@ -18,6 +18,27 @@ Packetimpact aims to provide: * **Control-flow** like for loops, conditionals, and variables. * **Flexibilty** to specify every byte in a packet or use multiple sockets. +## How to run packetimpact tests? + +Build the test container image by running the following at the root of the +repository: + +```bash +$ make load-packetimpact +``` + +Run a test, e.g. `fin_wait2_timeout`, against Linux: + +```bash +$ bazel test //test/packetimpact/tests:fin_wait2_timeout_linux_test +``` + +Run the same test, but against gVisor: + +```bash +$ bazel test //test/packetimpact/tests:fin_wait2_timeout_netstack_test +``` + ## When to use packetimpact? There are a few ways to write networking tests for gVisor currently: |