Each recipe is one real setup: your tools, what to say to Certyn in the chat, what it does, what you get, and what does not work yet. You do not need to set anything up first. Say the request, and Certyn sets up what it needs as it goes.
Test the product itself
- Explore a New Feature Before Release, Get Bugs and Test Cases
- Release Go/No-Go for Staging, from Runs, Issues and Pass Rate
- Reproduce a Customer's Bug Report from Support, with Steps and Evidence
- Turn a Jira Story, a Spec or a PRD into Test Cases, Then Run Them
- Test Your API from Its OpenAPI Spec
- Accessibility Check of Your Key Pages
- Performance Check of a Slow Page
Environments, accounts and data
- Test Each Pull Request's Preview URL (Vercel, Netlify)
- Read-Only Smoke Check on Production, on a Schedule
- Several Roles (Admin, Member, Guest), Each with Its Own Test Account
- Stripe Test Mode Payments and Feature Flags (LaunchDarkly or Similar)
Releases and versions
- Plan Release 2.6.0 with Notes, a Target Date and Tests for What Changed
- Follow One Version from Dev to Staging to Production
- Compare Releases 2.5 and 2.6, New Issues, Pass Rate and Likely Regressions
- Retest a Bug When Its Fix Version Reaches Staging, Then Close It as Fixed in That Version
- Hotfix 2.5.1 on Production, a Read-Only Smoke Check and a Retest of the Bug
- Write Release Notes for 2.6.0 from Fixed Bugs, Open Bugs and Test Runs
Plan the week and keep the suite healthy
- Weekly QA Plan (Agenda) That Certyn Proposes and You Approve
- Find Coverage Gaps and Fill Them with Test Cases
- Keep the Suite Healthy, Quarantine Flaky Tests, Review and Retire Old Ones
- Weekly QA Report for Managers, with Pass Rate, Trends and Open Bugs
- Triage Findings in Review, Confirm or Close Each with a Reason
Teach Certyn your product and team
- Teach Certyn Your Product with the Wiki, Testing Rules and Memory
- Write a Team Skill, for Example "How We Test Checkout
- Invite a Teammate and See What Setup Is Left
Errors, logs and other environments
- A Sentry Error Becomes a Reproduced Bug with Evidence
- Connect Your Own MCP Server (Logs, Metrics, an Internal Admin Tool)
- API Checks Written in Hurl, Run After Each Deploy
- Dev and Staging as Separate Environments, Compared Side by Side
Bigger jobs across your tools
- Customer Complaint to Issue, Code Pointer and Regression Test PR
- Check Your Getting-Started Guide and API Docs by Running Every Example
- Scripts That Create and Clean Up Test Accounts Through Your API
- Dashboard, API and CSV Export Show the Same Numbers
- Act Out a Customer's Whole Workflow, Find Awkward Steps and Missing Features
- Two Test Organizations, One Cannot See or Change the Other's Records
- Rehearse a Database Migration on a Throwaway Environment
- Stripe Webhooks End to End, Subscription Changes and Duplicate Events
Run the tests you already have
- Playwright Suite in GitHub, Public App
- Run Your Playwright Suite Every Night
- Cypress Tests in GitLab, Run After Each Deploy
- Selenium (Java) in Jenkins, App Behind a VPN
- Selenium (Python) with pytest on Certyn's Cloud
- Selenium (C#) with NUnit on Your Runner
- WebdriverIO Suite, Run the Way Your CI Runs It
- Postman Collection with Newman Against Staging
- k6 Load Script on Your Runner
- Test Your App on Localhost While You Develop
Write or fix tests in your repo
- Playwright Test for a New Feature, in Your Team's Style, as a PR
- Fix a Flaky Test, Find the Cause, Open a PR
- A UI Change Broke Many Tests, Fix Them in One PR
- Move a Selenium Suite to Playwright, One Area per PR
- Playwright and GitHub Actions in an Empty Repo
- Write Tests for What Each Merge Changed
CI and triggers
- Smoke Suite on Every GitHub Pull Request, as a Check and a Comment
- GitLab CI Calls Certyn After Deploy and Gates on the Result
- Push JUnit Results from Jenkins, Azure DevOps, CircleCI or Bitbucket
- Run a Certyn Process After Each Deploy
Where issues and test cases live
- Bugs Go to Jira with Evidence, Certyn Retests After the Fix
- Bugs Go to Linear or GitHub Issues
- Run TestRail Suites and Write the Results Back
- Run Zephyr Scale, Xray or Azure Test Plans Suites
- Send a Confirmed Bug to GitHub Copilot for a Fix PR
Hard sign-ins, mobile and desktop apps
- App with 2FA from an Authenticator App
- Sign-Up Flow with an Email Confirmation Code
- Mobile App on BrowserStack, Sauce Labs, LambdaTest or Your Own Appium Server
- Desktop App (Windows or macOS) Through Your Appium Server
Use Certyn from other tools
More ways to test
- Mobile and Tablet Layouts of Your Web App
- Dark Mode, Reduced Motion and Print Views
- Time Zones, Midnight and Daylight Saving, and Content by Location
- File Uploads with Images, PDFs, CSVs, Wrong Types and Too-Large Files
- Missing Translations, Cut-Off Text and Local Formats in Each Language
- Which Run to Start, How Long It Takes and What It Costs
Day to day
- Start Your Day with the Inbox, What Needs You and Last Night's Results
- Watch Certyn Live, Step In for a Captcha, Code or SSO, and Stop a Run
- A Run Got It Wrong, Fix the Verdict, Run It Again, Teach Certyn
- Attach a Screenshot, Log or HAR File in the Chat, Mention Issues with @, Use / Commands
- Report a Bug You Saw in Your Own Browser
- Mention @Certyn on a Jira or Linear Issue, Ask About the Bug, Start a Retest
When something goes wrong
- Certyn Cannot Reach Your App (IP Allowlist, Basic Auth, WAF or VPN)
- Sign-In Blocked by a Captcha, SSO, a Bot Check or an Email Code
- Runs Use Too Much Plan Time, Find What Uses It and Cut It
Results to your own systems
- Send Certyn Events to Teams, Discord or a Data Warehouse with Webhooks
- Use Certyn's REST API from Your Own Scripts
Your stack is not here? Ask Certyn in the chat. It combines the same pieces: runs with any goal, schedules, your CI, your repo and your own runner.