For developers who want Certyn to test a change on their own machine, before it reaches staging.
Your setup
- Your app runs on your laptop, for example
http://localhost:3000. - Docker Desktop (Mac, Windows) or Docker Engine (Linux).
- You want Certyn to check a page or a flow while you work on it.
Say this to Certyn
My app runs on localhost:3000 on my laptop. Test the new signup page there.
What Certyn does
- Opens the runner form. Paste its
docker runcommand in a terminal on your laptop. The form waits until the runner is online, then sends the default environment's runs to it. - Sets the environment URL to
http://host.docker.internal:3000. Inside a Machine,localhostis the Machine itself, not your laptop. The form's command adds--add-host=host.docker.internal:host-gateway, so this name works on Linux too. - On Linux, checks that your dev server listens on
0.0.0.0, not only on127.0.0.1(for examplevite --host 0.0.0.0). - Starts a Machine on your runner and tests what you asked, while you watch.
What you get
- Findings in the chat while you work.
- Issues for real bugs, when you ask.
- A check of your change before you push it.
Limits
- It works only while your laptop is on, the runner container runs, and your dev server is up. Do not schedule runs here; use a shared environment for that.
- The runner form routes the project's default environment. If that is a shared staging, its runs would go to your laptop. Add a
localenvironment for this URL, set its Execution target to your runner in Environments, and set staging back to Cloud-managed. - Each Machine uses your laptop's CPU and memory (by default 1 CPU core and 2.5 GB).
- On Linux, an app bound only to
127.0.0.1cannot be reached from the Machine.