https://github.com/acidghost/msgbounds-tester

Test how servers respond to different ways of interacting with it
https://github.com/acidghost/msgbounds-tester

Last synced: about 2 months ago
JSON representation

Test how servers respond to different ways of interacting with it

• Host: GitHub
• URL: https://github.com/acidghost/msgbounds-tester
• Owner: acidghost
• Created: 2021-04-16T17:19:03.000Z (over 3 years ago)
• Default Branch: main
• Last Pushed: 2023-02-25T07:56:16.000Z (almost 2 years ago)
• Last Synced: 2024-06-19T16:25:06.546Z (6 months ago)
• Language: Go
• Homepage:
• Size: 2.32 MB
• Stars: 0
• Watchers: 3
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# msgbounds-tester

Test how servers respond to different ways of interacting with it such as:

- sending multiple messages at once (i.e. as a single syscall);

- reading replies or not;

- reading replies thoroughly or not;

- different read timeout;

- amount of delay between sent messages (if any);

- closing the socket right after sending the last message or after the server exits.

## Usage

Build container image for desired target with `make $target`.

Start container (e.g. `docker run --rm msgbounds:$target -h` for help).

Start the container with environment variable `DO_STRACE=1` to run the tester (and target) under

`strace` to trace some useful syscalls. The output is stored in `/work/strace.log`.

The scripts should also produce the coverage of the target into `/work/cov.json` (from gcovr).