Skip to content
certyn logoCertyn
Start Free
RecipesDoc

Dev and Staging as Separate Environments, Compared Side by Side

Certyn adds your environments with their own URL, accounts and variables, runs the same checks on each, and tells you what differs.

For teams with more than one deployment of the same app who want each one tested, and the differences found.

Your setup

  • The same app on dev (https://dev.example.com) and staging (https://staging.example.com).
  • A different test account on each, and some settings that are the same everywhere.
  • You want to know if a flow works on staging the way it does on dev.

Say this to Certyn

Add our dev and staging environments: dev is https://dev.example.com, staging is https://staging.example.com, and staging is the default. Then run the signup flow on both and tell me what is different.

What Certyn does

  1. Lists the environments the project has (app.environment.list), then adds each one with a key and a URL (app.environment.create, you approve). Staging becomes the default: runs use it when you do not name one.
  2. Opens the sign-in form once per environment, so each one gets its own test account.
  3. Saves values that are the same everywhere as project variables (app.variable.set with project: true), and values that differ on the environment. When both have the same name, the environment's value wins.
  4. Says the run length and starts the same run on each environment (app.run.create with environment). For a suite, it runs the process once per environment.
  5. Reads both run reports and lists what differs: steps that fail on one only, different messages or data, pages missing on one.

What you get

  • One run report per environment, and issues that record the environment and version where they were found.
  • A short list of differences, with the evidence from each run.
  • If you ask: a schedule or an after-deploy trigger per environment (app.process.trigger.set). Each environment keeps its own rules.

Limits

  • No built-in compare view. Certyn compares two run reports, so use the same steps and similar test data on both.
  • The chat's Machine starts with the variables of the environment selected in the header. To check the other one, start a run there, or ask in a chat opened on that environment.
  • A self-hosted runner set up from the chat serves only the default environment. For the others, set Environments → Execution target.
  • Deleting an environment is permanent (you approve).
PreviousAPI Checks Written in Hurl, Run After Each DeployNextMobile and Tablet Layouts of Your Web App