Tester bug reports and launch QA
Ybug or Launch Ready? Two different jobs in the same launch
Ybug is a visual feedback and bug-reporting tool: clients, testers and users mark up the page they are on and send a report with an annotated screenshot, browser details and the browser console log. Launch Ready is an automated pre-launch QA check: it crawls a staging or live site with fixed rules and reports launch blockers, with evidence, in a report the client can read. Choose Ybug to collect what people find while they test, and Launch Ready to check each crawled page the same way before they start.
Last reviewed
Ybug and Launch Ready at a glance
| Question | Ybug | Launch Ready |
|---|---|---|
| What it is built for | Visual feedback for websites and web apps. People submit annotated screenshots and comments directly from the site. (Source: Ybug homepage) | Automated pre-launch website QA for agencies: it crawls a staging or live site, applies fixed rules and produces a prioritised fix list and a readiness report. |
| How issues are found | People find them, through a feedback widget or browser extension: they click the button, mark the page, add a note and send it. Ybug's pre-launch testing page describes a person walking the staging build with their own launch checklist. (Source: Ybug homepage, Ybug pre-launch testing) | The scanner finds them. It crawls the site and applies the same rules on every scan, across technical reliability, SEO and indexability, analytics, placeholder content, form markup, performance, and accessibility and compliance signals. |
| Who uses it | Ybug names agencies, startups, developers, project managers, testers and QA, and freelancers. (Source: Ybug homepage, Ybug pre-launch testing) | The agency's developer, technical lead or delivery manager, before the client sees the site. |
| What the client receives | Clients and testers send feedback from the page without signing in. Ybug's pricing page lists custom branding and hiding Ybug branding among its plan features. (Source: Ybug homepage, Ybug pricing) | A readiness report the client can read, as a share link or PDF: findings with evidence, what ran clean and what was not measured. The Agency plan adds your logo, colours and a client portal. |
| Where it fits in the delivery week | While people test. It runs on staging, preview and password-protected builds, and installs as a snippet, an npm package, a browser extension or through CMS and tag manager guides. (Source: Ybug pre-launch testing, Ybug installation docs) | Before the client review: scan staging, fix, scan again. Then once more before go-live, and the report goes out with the handoff. |
Choose Ybug when…
- Clients, testers or users should report problems from the page itself: click the button, mark the page, add a note and send it, without signing in. (Source: Ybug homepage)
- Developers need the console log from the reporter's session, with stack traces and line numbers, and, when network logging is on, the requests and failed resources. (Source: Ybug console logs)
- The build is on staging, a preview or behind a password, or only reachable through a login or VPN that your testers can use. (Source: Ybug pre-launch testing)
- A screen recording would explain a problem better than a screenshot. (Source: Ybug homepage)
- Passwords, tokens and card details should be anonymised in the screenshots people send. (Source: Ybug homepage)
- You want reports sent to a tool such as Jira, Linear, GitHub, GitLab, Asana, Trello or Slack. (Source: Ybug integrations)
Choose Launch Ready when…
- You want the same checks on every client launch, whoever is on the project that week.
- You want to catch a leftover noindex tag, a form still posting to staging, tracking that never fired, a broken link or placeholder text before the client opens the site.
- You want a report to hand over with the site: findings with evidence, what ran clean, and which checks were not measured.
- On a paid plan, you want Fix this to open a pre-filled GitHub or Linear issue, give Jira and Asana text to paste, or write a prompt for your AI coding tool.
How we scan · See an example report · Agency website QA guide · Website launch checklist
Using both
Ybug's own pre-launch workflow has a person walk the staging build, run through a launch checklist and pin issues as they go. (Source: Ybug pre-launch testing)
Run Launch Ready before that walk. The scan checks each page it crawls for the rule-checkable problems, so the people testing can spend their time on what needs a person: submitting forms, logging in, checking out, and how each page looks on their device.
Scan again after the fixes and before go-live, and send the report with the handoff.
What Launch Ready does not do
- It does not collect feedback from people or annotate pages, and it does not record a browser session.
- It never logs in as a site user. For a password-protected staging site, it can send the HTTP Basic Auth credentials stored on the project.
- It does not guarantee a bug-free website.
- It does not submit forms or run functional tests. Form checks read the form markup; they do not confirm that a message arrives.
- It is not a full accessibility audit, legal review or security test. Its accessibility and compliance checks are automated signals.
- Evidence on a finding is the affected URL and what the rule found. The report shows one homepage screenshot, not a screenshot for each finding.
- It does not make the launch decision. People make it, with the report in hand.
Sources
Statements about Ybug come from these official pages. Features and plans change; check the current page before you decide.
- Ybug homepage, read
- Ybug pre-launch testing, read
- Ybug console logs, read
- Ybug integrations, read
- Ybug installation docs, read
- Ybug pricing, read
Scan your next client site before the review
Add the staging or live URL, read the fix list, and send the client a report when it is ready.