Quick Start
Get started with Kerno in minutes
Requirements
Getting started
Running your first test with Kerno
Last updated
Get started with Kerno in minutes
For Kerno to work you'll need:
Docker installed and running on your machine so Kerno can start the test environment.
If you're using a VPN service Kerno will not be able to connect to LLM providers and therefore won't be able to index your codebase and run tests
Sign up for your Kerno account here.
Install the Kerno extension from the VS Code Marketplace or the Open VSX Directory.
Kerno is currently available on VS Code, Cursor, Windsurf, and Antigravity.
When you open your project, Kerno begins indexing your code and setting up a test environment. Wait for the progress dot to turn pink, which shows that indexing is complete and the environment is ready. If anything goes wrong, check the troubleshooting section or contact the engineering team on Slack.
Indexing a new project might take a few minutes to complete for large codebases.

Select any endpoint to begin adding coverage. Kerno will create a suite of test scenarios for this endpoint and use these scenarios as a baseline for future runs.

When creating tests for a new endpoint, Kerno will take 1-2 minutes to create the full test suite. When you run tests for the same endpoint the process will take a few seconds.
Update your endpoint code, save your changes, and run Kerno again. Kerno reviews the update and runs the scenarios it created earlier to detect any differences. It reviews body responses, headers, and status codes.

When you save your code changes, Kerno will update the index and restart your service. This might take a 10-20 seconds.
When the tests finish, Kerno produces a report that lists all detected differences. You can approve the differences and update the tests, or you can adjust your code and run the tests again until the difference is resolved.
If you approve the difference, Kerno updates the tests to reflect the new behavior. It also adds or removes tests when the logic of your endpoint has changed.
If you encounter issues or have questions, message us on Slack, and we’ll gladly help.
Last updated