Skip to content
Certyn

Projects & Environments

Projects scope your app; environments define where and how sessions run.

Projects and environments answer two basic questions:

  • What application are we operating against? (Project)
  • Where should agent sessions run, and with which settings? (Environment)

Projects

A Project is the top-level container for a single application or service. It groups:

  • processes (suites)
  • tests (test cases)
  • runs and issues
  • wiki context

One project per deployable app

Keep each deployable web app or major surface area in its own project to keep runs and issues easy to interpret.

Starter project is created automatically

On your first sign-in, Certyn creates a starter project and a default Production environment, then shows an onboarding wizard to connect your app and run live testing.

Environments

An Environment is a named target like staging or production. Environments are where sessions actually run.

Each environment can include:

  • Base URL: where to start navigation (for example https://staging.example.com)
  • Variables: key-value pairs that the agent can use (credentials, test data)
  • Model selection: which model sessions should use in this environment
  • Version: optional version string and changelog, used for traceability and triggers

Managing environments

Use the environment selector in the header and click Manage Environments.

Environment variables

Variables are passed to the agent in the session context as a dictionary (by name). Certyn does not require a special placeholder syntax in your tests.

Example variables:

LOGIN_USERNAME=qa@example.com
LOGIN_PASSWORD=...
SEED_ORDER_ID=12345

In a test, write instructions like:

Sign in using LOGIN_USERNAME and LOGIN_PASSWORD from the environment variables.

Avoid production secrets

Use dedicated test accounts and staging data. Do not put real customer credentials into environment variables.

Switching environments

Most of the UI is environment-aware (runs, issues, processes). Switching environments changes what you are operating against and how sessions are configured.

This lets you:

  • verify a fix in staging
  • run targeted checks in production when needed
  • keep credentials and data separated per environment
PreviousWiki & ContextNextProcesses & Tests