Testing

Testing is the kis.ai test execution framework. You define tests in YAML and run them with the kis test CLI: functional API testing over HTTP, gRPC, and SQL, with scriptable steps, assertions, and templating. The same test definitions drive load testing, so a functional suite can become a load workload without rewriting it.

Runs stream results to the console and exit non-zero on failure, so Testing drops straight into CI. When you need scale, the same definitions run distributed across a pool of agents coordinated by an orchestrator, and results can be captured as JUnit, log files, or a queryable result store.

Continue with

• Getting started — build the CLI, write your first API test and first load test, and pick the right runner.
• Test definitions — the YAML schema: suites, tests, and steps; HTTP, gRPC, SQL, and script step configs; hooks and tags.
• Assertions and variables — the assertion grammar and operators, Liquid templating, variable scope, and extracting values from responses.
• Data-driven tests — table-driven execution and CSV fan-out for running one test across many rows of input.
• Scripting — script steps and plugin actions: supported languages, the test.* API, and built-in functions.
• Load testing — profiles and phases, the execution model, the metrics you get back, and sizing guidance.
• Server modes — distributed execution with an orchestrator and agents, the HTTP API, and configuration.
• Outputs — console output, JUnit reports, result storage, and log files.
• CLI reference — every command and flag: test, tests, load, api, agent, and orchestrator.