What WAVE does
WAVE is test automation for your backend.
What a test can do
| Systems it has blocks for | HTTP and HTTPS APIs. Kubernetes. SQL databases. OpenSearch. SFTP. Linux servers over SSH. |
|---|---|
| Network checks | Ping, and a TCP or UDP port check. |
| Several systems in one test | A later block can use a value an earlier block got from a different system. |
| Linux servers | Over SSH, directly or through any number of jump hosts. Once a test has connected to a server, it can run one command, run a whole script, or forward a port. |
| Remote execution | A remote section is a group of blocks that runs on the server at the other end of an SSH session. Blocks that cannot run there stay on your machine, and each block shows where it runs. That server needs Python already installed. WAVE installs nothing on it and leaves nothing behind. |
| Control over the connection | On an HTTP request you set how redirects and retries behave, which TLS versions and ciphers WAVE offers, and which client certificate it presents. On SSH you set the host key policy. |
| Files and formats | Read, write, copy, move and delete files. Parse CSV, Excel, XML and JSON. |
| Your own code | Run Python or a shell command as a block. Pass values in, and take values out. |
| Systems without a block | If you can reach a system from a command line or from Python, a test can reach it the same way. |
Where it runs, and what leaves the machine
| Where it runs | On your own machine, on your own network. No account to create. |
|---|---|
| Operating system | Linux. |
| Connections out | No telemetry, no update check. Every connection out is one you started, to an address you set. |
| Without internet access | Runs on a network with no internet connection, once it is installed. |
| Your data | Tests, credentials, hosts, results and reports stay on your machine. If you connect an AI assistant to WAVE, what it reads goes to the model that assistant uses. |
| Debug traces | If you hit a bug in WAVE, you can collect a trace and send it with a bug report. You choose what goes in the trace, and you can report a bug without one. |
| Secrets | Any variable can be marked secret. By default, a secret is masked as ******** everywhere it appears: in logs, in reports and on screen. It is encrypted when it is saved. |
Building a test and running it
| Control flow | If and else, switch, loops with break and continue, branches that run in parallel, try, catch and finally, wait until a condition is true, delay, assert, and stop the run. |
|---|---|
| Passing a value on | You choose which of a block's outputs to keep, and you name the variable that holds each one. Later blocks read that variable by name. |
| Calculating a value | A variable can hold a Python expression instead of a fixed value. WAVE calculates it the first time a block reads that variable, and keeps the value until the run ends. For anything longer than one expression, use a Python block. |
| Watching values during a run | Every variable is listed while the test runs, and its value updates as the run continues. Open one and you see its initial value and its current value. |
| How a run is started | From the app, through a REST API, or from an AI assistant connected to WAVE. |
| MCP server | It is off until you turn it on. In the app's settings you choose whether it listens on localhost only or on your network, and whether it asks for a username and password. Your assistant can read the tests you already have, write a new one or change one, group tests into suites and regressions, start a run, and read the results. |
| AI inside WAVE | There is none yet. WAVE calls no AI model. |
Regression"Nightly"
Suite"Orders service"
Test"Checkout health"
Block
SSHOpen session
HTTPGet order status
SQLRead order row
AssertStatus matches
Test"Refund flow"9 blocks
Suite"Billing"4 tests
When a test fails
| Breakpoints | Set them before the run, or while the test is running. |
|---|---|
| While paused | Look at any value the run is holding, and change it before you continue. |
| Stepping through a run | Step over a block, step into it, run the paused block again, skip one, or continue. |
| Running one block | Run a single block on its own, or start the run at any block in the test and let the run continue from there. |
What a run leaves behind
| The report | Every run has a report. It shows how long each block took, who started the run, and the full log. |
|---|---|
| Sending a report to someone | Export it as one HTML file. You can also export it as JSON. |
| Past runs | WAVE saves every run started from a test, suite or regression page, or through the REST API or MCP. A saved run is a read-only snapshot of the test as it ran. Open it and you see every block with the status it ended in, and the values the run held at the end. |
| Run artifacts | A saved run keeps the files it wrote. You can browse them and download them. |
Handing a test to someone else
| Reading a test | A test is a diagram, not code. |
|---|---|
| Where tests are stored | As plain text files, under one directory that you choose. Values you mark secret are encrypted inside those files. You can keep the directory in version control, where a change to a test shows up as readable text. |
| Moving tests between machines | Export tests, suites and test data on one machine, and import them on another. |
Functions
| What a function is | A piece of a test you build once and publish to your team's library. Anyone on your team can drop it into their own test as one block. |
|---|---|
| What a function can see | Only what you pass in. It cannot change the variables of the test that uses it. Anything it produces comes back through its outputs. |
| Versions | What is inside a published version never changes. A function block binds to one version, and publishing a newer version does not move it. You move it yourself, by opening that block and choosing another version. |
| Breaking changes | Some changes can only go out as a new major version: removing an input or an output, renaming one, changing the type of one, or making an input required. |
| Moving functions between machines | Export a function with its version history, and import it on another machine. |
Function"Wait for telemetry lock"
v1.0.0"Nightly pass check", "Payload command path"
v1.1.0"Launch rehearsal"
v2.0.0"Ground station failover"
Profiles
| What a profile is | A named set of values. Each value can be different in each environment. You choose what a profile holds: the host and password a block needs to reach a system, a timeout, a tenant name. |
|---|---|
| How a test uses a profile | You attach a profile to the blocks that need it, and you give the profile an alias in that test. Those blocks read its values by that alias. |
| Choosing the environment | You pick the environment when you start the run, not when you build the test. |
| Secrets in a profile | Any value can be marked secret. When you export a profile you choose whether its secrets go out masked, still encrypted, or in plain text. Masked is the default. |
| Moving profiles between machines | Export a profile on one machine and import it on another. If the other machine does not have one of the environments, WAVE drops the values for that environment and tells you which environments it dropped. |
Test
"Health Check"
Profile"Orders service"
devstagingproduction
db_hostdb-dev.internaldb-stg.internaldb.internal
api_baseapi-dev.internalapi-stg.internalapi.internal
timeout_ms200050009000
tenanttenant-atenant-atenant-live