performance-testing

fortio has so many features that -h or the README.md or the web UI are not making for an easy onboarding or discovery of all it can do and how to best use it

default values of many flags too (like now using -a -uniform -nocatchup being more or less required for serious use etc

for now I added these to https://github.com/fortio/fortio/wiki/FAQ#i-want-to-get-the-best-results-what-flags-sho

https://k6.io/docs/using-k6/thresholds/

I'm trying a simple test with tcpliveplay but it seems tcpliveplay doesn't handle TCP handshake properly.
Let me describe the steps from my testing.

1. Logged as root on machine A I ran this command to capture all the traffic to the host 104.31.95.22 (my website).

# tcpdump host 104.31.95.22 -n -s 65535 -w http.pcap

2. In another shell instance under the same machine I performed a

We need to add more integration tests (living in the src/it folder) to cover various usage scenarios.

Right now we only have a single test that just checks that the plugin can run a basic test with no additional configuration (This can be used as an example on how to configure other integration tests). We should be testing various configuration options as well.

Requirements:

• The .jmx files

Specifically, Mocha seems to perform lots of operations like Array#includes and Array#indexOf on frozen arrays while setting up its environment and executing its tests.

It would be good to have this pattern reflected in the WTB.

Ref. https://docs.google.com/document/d/1X6zO5F_Zojizn2dmo_ftaOWsY8NltPHUhudBbUzMxnc/edit.