What is Certyn?

Certyn answers one question: can you ship? It gets there in three steps. It runs tests against your app, in a real browser by default and in Appium-backed Android or iOS sessions when a mobile runtime is configured. It records every result in one project with its evidence, including results it did not produce. It answers with what needs a person and whether the environment is ready to release.

Do I have to move my tests into Certyn?

No. Certyn is built to accept work it did not create.

Your CI suites: push Playwright JSON or JUnit XML to POST /api/ci/results and each run lands next to the runs Certyn started. See Bring Your Test Framework.
Your test management tool: connect TestRail, Zephyr Scale, Xray, or Azure Test Plans and Certyn pulls the current cases at run time and writes results back. See Connect a Test Management Tool.

You can also author cases in Certyn. Both work, and they work together.

Is Certyn a replacement for Jira/Linear/GitHub Issues?

No. The split is deliberate: your tracker stays the source of truth for ownership and planning, and Certyn is the source of truth for quality signal and its evidence. Certyn tracks internal work items so the audit trail stays intact, and links them out to your tracker.

Is Certyn a replacement for our CI dashboard?

It does not have to be. Push your results in and one page answers what the last commit did, next to everything else that ran. Plenty of teams keep their CI dashboard and use Certyn for the review queue and release call.

Do I need to write code?

No. Tests are written as natural-language instructions with explicit expected outcomes.

Can I watch runs live?

Yes. While sessions are running you can open the live view (for example from a process page via Watch Live).

Does Certyn support mobile apps?

Yes. Certyn supports Appium-backed mobile runtime projects for Android and iOS apps. You provide a reachable Appium server and app/device settings, and mobile-capable agents can inspect screenshots, read page source, tap, type, swipe, launch the app, change orientation, and report evidence.

For responsive websites, use normal web runs with mobile device emulation. For native or hybrid apps, use Mobile Runtime.

How do environment variables work?

Environment variables are passed to the agent as part of the environment context. In your tests, instruct the agent to use variables by name (for example: "Use LOGIN_USERNAME and LOGIN_PASSWORD from the environment variables").

Can I run on a schedule or from CI?

Yes.

Use process schedules (daily/weekly/cron) for recurring runs.
On GitHub, use certyn-one/action@v1.
On other CI systems, use the CI Runs API reference.

Do we need to change our gitflow to use Certyn?

No. Keep your current branch and release model.

Integrate Certyn at your existing decision points:

merge gates (PR checks)
deploy/promotion gates (post-deploy smoke)
nightly quality sweeps (regression)

How is usage measured?

Usage is measured in execution minutes (compute time) rather than "number of tests". This reflects how much agent runtime your runs consume.

What if a test is flaky?

Treat flakiness as a first-class signal:

quarantine unstable tests so they stop blocking important runs
make tests smaller and more deterministic
use stable test data and dedicated test accounts