BugBug HomepageContact SupportLoginSign up free
Search…
Documentation
Quick Start
What is test automation?
Start for free
Create your first project
Install Chrome extension
Create and run the tests
Creating Tests
Your first test
Duplicating tests
New test from here
Recording tests steps
BugBug overlay
Recording clicks
Recording hover
Recording keyboard typing
Recording assertions
Recording drag & drop
Record from here
Re-recording steps
Editing tests
Grouping steps
Components
Manually editing steps
Actions
Assertions
Tabs & iframes
Variables
Custom JavaScript actions
Running tests
Running the tests
Statuses
Run (locally)
Run in cloud
Schedules
Parallel runs
Running via API
Preventing failed tests
Waiting conditions
Smart click
Smart scroll
Selectors
Timeout
Delay / Sleep
Project settings
Debugging Tests
Runs history
Screenshots
Debug in Chrome
Run and stop after
Breakpoint
Organizing tests
Naming your tests
Searching tests
Suites
Components
Projects
Workflow Tips
Multiple environments
Testing registration & login
Integrating with build systems
Collaboration
Organizations
Inviting team members
Cloud runs limit
Integrations
CLI
Zapier
Slack
Github
Bitbucket
Gitlab
Trello
Jira
Your account
Account settings
Edit your profile
Forgot password
Manage Subscriptions
FAQ
Other links
BugBug Homepage
Pricing
Terms & conditions
Privacy Policy
Powered By GitBook
Screenshots
You can use screenshots to debug your tests and understand what was the reason for the failure.
When a test step is executed, BugBug automatically takes screenshots:
  • of the whole window
  • of the individual element
Click the screenshots to see the full preview.
BugBug also keeps the screenshots history, so that you can also compare screenshots from previous runs. Just go to the "Runs history" tab.
How long screenshots are kept? It depends on your subscription plan, learn more in pricing.
Debugging Tests - Previous
Runs history
Next - Debugging Tests
Debug in Chrome
Last modified 1mo ago
Copy link