Your first useful test

1. Install the CLI and its browser

Extract the ZIP and open the folder containing the package. Replace VERSION with the downloaded filename. Install NoryBot globally, then install the browser used to explore your application. Keep the quoted ${PWD}/ prefix to avoid Bun’s relative-path ENOENT error, including in folders with spaces.

bun add --global --ignore-scripts "${PWD}/norybot-VERSION.tgz"
norybot browser install

Updating an existing installation

On NoryBot 0.1.4 or later, check and install updates directly from the CLI. Interactive use shows a notice when a new version is available. Your projects, configuration and license are preserved. Use norybot update --rollback to return to the previous CLI, after checking migration notes.

norybot update --check
norybot update

On 0.1.3 or earlier, download the new version from your existing Polar purchase once. Remove the old global CLI first, then install the included package. This avoids Bun’s local-tarball dependency-loop error. Substitute the actual filename below. Keep the previous ZIP and back up your project evidence before upgrading.

bun remove --global norybot
bun add --global --ignore-scripts "${PWD}/norybot-VERSION.tgz"
norybot --version
norybot browser install

Removing the global CLI leaves your project files in place. Do not rerun initialization. Your project configuration, provider keys, generated tests, evidence and stored license remain outside the global package installation. Review release notes for database compatibility; installing an older CLI does not undo a migration.

2. Choose your framework

Open your application repository and choose the framework you want NoryBot to generate. Initialization writes the configuration and scaffolds the selected framework.

cd /path/to/your-project
norybot init --framework cypress

Prefer Playwright? Use norybot init --framework playwright. Run the framework installation command printed by initialization before continuing.

3. Connect AI and generate a small suite

Configure your AI provider key locally, then generate tests for an application you are authorized to use. Start with a simple, representative flow.

norybot generate \
  --url https://your-app.com \
  --feature smoke

Inspect the generated code, selectors, and assertions. The tests are editable files in your project; adapt them to your actual requirements.

4. Run and inspect

norybot run

Read failures before rerunning. Confirm that the tests exercise the intended flow and would fail if the application regressed.

5. Add security checks with Pro

Activate the license from Polar Purchases, then start with a scoped code scan or an authorized web scan. Evaluators can purchase when ready to use the Pro security workflow. Follow the license setup and read the security and data guide first.