Skip to content
Getting StartedDoc

Creating Your First Project

Create a project, configure environments, and set context for reliable verification runs.

A Project is the top-level container in Certyn. It groups your environments, tests, processes, runs, issues, and wiki context for a single application.

Your first project (automatic)

On your first sign-in, Certyn automatically creates:

  • a starter project (for example: "My Project")
  • a default Production environment, with no URL until you give Certyn your app's URL. Browser runs need one; work in your repo, CI and scripts does not
  • the standard processes: App Explorer, Smoke Suite, Regression Suite

Then you land in Ask Certyn. Tell it what to test, and it asks for the URL, a test account and where bugs should go, sets them up, and checks that it can reach and use your app. See the Quick Start Guide. Nothing has to be set up before you start: when a request needs something that is missing, Certyn asks for it then.

Configure Environments

Environments tell Certyn where to run sessions and what variables/models apply.

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

Most teams create environments like:

  • staging (recommended as default)
  • production (already created by default)

For each environment, set:

  • Base URL for web projects
  • Mobile runtime overrides for mobile projects that need environment-specific device or app settings
  • Variables (optional): credentials and test data keys like LOGIN_USERNAME, LOGIN_PASSWORD
  • Model (optional): which model to use for sessions in this environment
Public access required

Agent sessions run in Certyn's cloud. Web environment URLs and mobile Appium servers must be reachable from the internet, or from a self-hosted runner inside your network.

Create additional projects (optional)

If you operate multiple apps, create a project per deployable app.

Open All projects from the project switcher and click New. Give the project a name and say what it tests (a web app, an API, or a mobile app); Certyn then opens its Ask Certyn, where you set it up the same way.

Add Wiki context

Open Wiki and fill in:

  • Overview: primary users, critical flows, out of scope
  • Rules: stable statements that must always be true

This reduces ambiguity and improves both explorer decisions and issue quality.

Teammates

Invite teammates under Settings → Team, or ask Ask Certyn to invite someone by email.

Not a replacement for Jira/Linear/GitHub Issues

Certyn can integrate with external trackers, but your external tracker remains the source of truth for ownership and status.

What's next?