Record the bug once.
Show the steps that break it. Engineers see the page, the errors, and the moment, without a long thread.
When QA teams record.
Show the steps that break it. Shoyu keeps the page, the order of steps, and the errors if you choose.
The page you tested.
Title and address attach to the second you were there.
Errors and failed requests.
With Deep Context on, console errors and failed requests are pinned to the second.
The steps, in order.
The transcript and the markers list each step that you took.
None of this needs extra work. It attaches while you record.
How context worksTypeError: total is undefined cart.ts:42
POST /api/cart 500 412 ms
Enhance your recording with Studio.
Open any recording in Studio before you share it. Viewers can still watch the original.
Skips
Skip the setup and keep the part where it breaks.
See the Skips toolSpeed
Speed up steps that repeat.
See the Speed toolMarkup
Circle the part that is broken.
See the Markup tool
What everyone else gets from QA teams’ recordings.
Nobody else has to record to benefit. This is what they get when QA teams do.
Engineering teams
Reproduce at once, with the page and the error.
Product teams
Judge how bad it is from the video, not a summary.
Support teams
Answer “is this a known bug?” by searching.
Design teams
See exactly where the interface breaks.
How QA teams use Shoyu.
Report a bug.
Record the steps. With Deep Context on, console errors and failed requests are pinned to the second.
Check a fix.
Record the retest and link it to the first report. Everyone sees the change.
Share a test pass.
Walk through a release. Anyone can watch what was checked.
What QA teams get from watching.
Recording is half of Shoyu. Watching other people’s recordings saves QA teams time too.
Watching an engineering team’s Shoyu
See how a fix works, so you know what to retest.
How engineering teams use ShoyuWatching a design team’s Shoyu
See what a flow should do before you test it.
How design teams use ShoyuWatching a product team’s Shoyu
Hear what “done” means for a feature.
How product teams use ShoyuWatching a support team’s Shoyu
See customer reports to turn into test cases.
How support teams use ShoyuWatching a marketing team’s Shoyu
Learn which promises need a test.
How marketing teams use ShoyuWatching an agent team’s Shoyu
Check agent changes quickly, and test the risky step.
How agent teams use Shoyu
Features that help.
Browser context
The page, and errors if you turn them on.
How Browser context worksRelated recordings
Link a retest to the first report.
See featuresSearch
Find every recording of the same page.
See Search
Engineers
Designers
Product managers
Support
Marketers
Agents