Testing & Tooling

Vango’s tooling is part of the framework contract. The goal is not just to build pages, but to keep routes, persistence, and reactive behavior auditable as the app changes.

Core Commands

1vango dev
2vango gen routes
3vango gen bindings
4vango state plan
5vango state apply
6vango build
7vango test
8vango lint
9vango test schema
10go test ./...

vtest

pkg/vtest is the main way to test stateful Vango components without driving a full browser.

Use it for:

• clicking buttons by data-testid

• submitting forms

• asserting stateful UI transitions

• verifying render output around live interactions

Route And Docs Testing

For public routes:

• use HTTP tests for page rendering and mounted docs routes

• use vtest for stateful component interactions like nav toggles or code tabs

What To Regenerate

When routes or stateful surfaces change, regenerate:

• routes_gen.go

• state artifacts

• bindings when required

CI should verify:

• routes are up to date

• bindings are up to date

• state artifacts are up to date

• warm versus cold deploy impact is explicit

For native iteration, the current guide includes:

1vango run macos
2vango build macos
3vango package macos
4vango run ios
5vango build ios
6vango archive ios
7vango export ios

Troubleshooting Mindset

If something “sort of works” but feels unstable, check these first:

1. list identity and keyed rendering

2. DOM ownership boundaries

3. async work placement

4. route generation and state artifacts

5. runtime mount path, WebSocket proxy behavior, and dev reload socket health