Visual bug handoff
Record a short bug-report video from a reproducible URL
Use a five-second MP4 when a screenshot cannot show delayed rendering, loading behavior, or animation. Attach the downloaded file with exact reproduction notes so the recording has context.
export SCRNIFY_API_KEY=...
video_url="$(scrnify capture "$BUG_URL" \
--type video --format mp4 \
--width 1440 --height 900 --duration 5)"
curl -fsSL "$video_url" -o bug-report.mp4Issue attachment
bug-report.mp4 — five seconds of the URL-reachable page state after the configured lifecycle wait.
Run sheet
Use motion only when motion explains the bug
- 01
Choose a stable reproduction URL
Deploy the broken state somewhere the hosted Capture service can reach. Put steps, expected result, and actual result in the issue; the video should support those details, not replace them.
- 02
Pick a short duration
Start with five seconds for an animation or loading-state defect. Video uses one metered usage unit per recorded second, so capture only the interval needed to show the behavior.
- 03
Fix the viewport
Set width and height when responsive behavior matters. Record those dimensions in the report so maintainers know which layout they are seeing.
- 04
Download and attach
The CLI returns an asset URL. Download the MP4, verify it opens, then attach it through the issue tracker or CI artifact mechanism you already use.
Before sharing
Write a report maintainers can replay
- Include expected and actual behavior in text; video alone is hard to search and easy to misread.
- Record target URL, viewport, capture duration, and commit or release identifier.
- Avoid personal data and secrets visible on the target page before sharing the recording.
- Use a still screenshot instead when one frame shows the defect more clearly and cheaply.