Getting Started
Introduction to Certyn
Learn what Certyn is, how it works, and how to use it as a QA team for your app.
Certyn is a QA team for your app. You configure where to test, provide lightweight product context, and define what "good" looks like. Certyn runs browser-based verification workflows, checks key flows, watches open issues and live errors, produces evidence, and shows what is still in the way before you ship.
Why Certyn?
Traditional test automation is expensive to write and painful to maintain. Selectors break, page structures change, and test suites drift. Certyn takes a different approach:
- Automate repetitive QA work, not judgment: Certyn runs and reports; humans review decisions.
- Tests in natural language: describe intent and expected outcomes without writing brittle locator code.
- Real browsers in isolated sessions: each session runs in its own container and records artifacts.
- Evidence-first results: logs, screenshots, and traces make failures actionable.
- Continuous and triggerable: run on schedule, on-demand, or from CI.
How It Works
- On your first sign-in, Certyn automatically creates a starter Project and a default Production environment.
- Certyn opens an onboarding wizard where you connect your app (base URL + optional login credentials) and watch live testing.
- When onboarding completes, Certyn marks the system as ready, starts the App Explorer baseline run, and activates the standard processes (Smoke Suite and Regression Suite) so they run on their schedules/triggers.
- Fill out the Wiki (overview + rules) so Certyn has stable product truth.
- Runs create isolated Sessions that produce artifacts and create Issues when something breaks or looks suspicious.
Who Is Certyn For?
- Teams that want continuous quality coverage without expanding QA headcount.
- Developers who want evidence-rich failures and fast verification loops.
- QA leads who want to spend time on strategy and edge cases instead of re-running regressions.