Starting a Recording
1
Navigate to the Issue
Go to the page or state where the bug occurs
2
Click the Kasava Icon
Click the extension icon in your toolbar
3
Select Product
Choose the Product this bug relates to (optional)
4
Click Record
Click the red record button to start
5
Choose Screen
Select which screen or tab to record
Recording Techniques
Show the Expected vs Actual
Demonstrate what should happen and what actually happens:- Explain what you’re about to do
- Show the expected behavior (if possible on another page/state)
- Demonstrate the bug
- Highlight the difference
Narrate Your Actions
Speak while recording to provide context:- Describe what you’re clicking
- Explain what you expected to happen
- Point out what went wrong
- Mention any relevant background
Reproduce Consistently
If the bug is intermittent:- Describe the conditions when it occurs
- Show multiple attempts if possible
- Note any patterns you’ve observed
Keep It Focused
- Record just the relevant portion
- Avoid unnecessary navigation
- Trim mental pauses by using pause/resume
- Aim for 30 seconds to 2 minutes
What Gets Captured
Video
The extension records your screen with:- Full resolution capture
- Cursor movements
- Scroll actions
- UI interactions
Audio
If enabled, the microphone captures:- Voice narration
- System audio (optional)
Console Logs
Automatically captured:console.logmessagesconsole.warnwarningsconsole.errorerrors- Unhandled exceptions
Network Requests
The extension logs:| Data | Captured |
|---|---|
| URL | Yes |
| Method | Yes |
| Status Code | Yes |
| Response Time | Yes |
| Request Headers | Limited |
| Response Body | Limited |
For privacy, request and response bodies are only captured for failed requests (4xx, 5xx status codes).
Page Metadata
Each recording includes:- Page URL
- Page title
- Browser version
- Operating system
- Viewport size
- Timestamp
Recording Quality
Optimal Conditions
For best recordings:- Close unnecessary tabs
- Disable notifications
- Use a clear microphone
- Ensure stable internet
Quality Settings
| Setting | File Size | Clarity | Upload Time |
|---|---|---|---|
| High | Large | Best | Longer |
| Medium | Moderate | Good | Moderate |
| Low | Small | Acceptable | Fast |
After Recording
Stopping the Recording
Click the stop button or use your keyboard shortcut. The recording will:- Stop capturing
- Process the video
- Begin uploading
- Show upload progress
Adding Details
After upload, you can add:- Title (auto-generated from AI, editable)
- Description (auto-generated, editable)
- Priority
- Labels
AI Analysis
Kasava’s AI automatically:- Transcribes your narration
- Identifies the type of bug
- Extracts reproduction steps
- Suggests severity
- Links to relevant code (if available)
Best Practices
Do
- Show the bug clearly
- Narrate your actions
- Include console errors in frame
- Show error messages clearly
- Mention reproduction frequency
Don’t
- Record sensitive data (passwords, API keys)
- Include personal information
- Make recordings longer than necessary
- Rush through complex reproductions
- Assume context is obvious
Recording Types
Visual Bugs
For layout or styling issues:- Zoom in on the problem area
- Compare with expected design
- Check multiple viewport sizes
- Note browser-specific behavior
Functional Bugs
For broken features:- Start from a clean state
- Show complete user flow
- Capture all error messages
- Check network responses
Performance Bugs
For slow or laggy behavior:- Record during slow periods
- Show timing expectations
- Note when it started
- Check network waterfall
Troubleshooting Recordings
Recording is blurry
Recording is blurry
Increase quality settings in the extension. Ensure your display resolution is detected correctly.
Audio is too quiet
Audio is too quiet
Check microphone volume in system settings. Speak closer to the microphone.
Recording stopped unexpectedly
Recording stopped unexpectedly
Recordings have a maximum duration. Check the max duration setting. Also ensure you didn’t navigate to a restricted page.
Console logs missing
Console logs missing
Some pages block the injection script. This is normal for pages with strict security policies.