Sample reports
Sample reports show the format of what you receive: a ranked findings report for AI testing, a handover guide for a Playwright suite, and a run summary from CI. They are being prepared using invented data, so no client information will appear in them.
What will the AI testing sample report contain?
A summary of what was tested, how the golden dataset was built, pass rates across repeated runs, and each finding with its severity, the exact conversation, how often it occurred and the area to fix. Every finding shows that a QA engineer reviewed it.
- What was tested, and what was out of scope
- How the golden dataset was built and approved
- Pass rate and variation across repeated runs
- Each finding: severity, exact input and output, frequency, area to fix
- Reviewer sign-off on every finding
What will the Playwright sample report contain?
An overview of the journeys covered, how to run the suite, an example HTML report with a failing test, the trace and video for that failure, the list of quarantined tests with reasons, and notes on how the code is organised so your team can extend it.
Why are there no real examples yet?
TBS Tech Services doesn’t show client work without written permission, and we won’t invent results. The samples will use made-up products and say so clearly. That is why this page describes the reports rather than showing them, and why real examples appear only when a client agrees in writing.
Can I see an example before I decide?
Send a quote request and tell us which report you want to understand. We reply by email and tell you what we can share at that stage. The methodology page also lists every check in the order the report presents it.
Ready to find out what is breaking?
Tell us what you’re shipping. We reply by email, and quote each project on its scope.