Taking Screenshots & Managing Cookies
Why Screenshots Matter in Automation
Screenshots are invaluable for debugging failed test runs, since they capture exactly what the browser looked like at the moment of failure - far more useful than reading an error message alone.
Capturing Screenshots in Selenium
Selenium provides a built-in method to save the current browser view as an image file. This is commonly triggered automatically whenever a test assertion fails, so developers can review it later without needing to reproduce the issue manually.
- driver.save_screenshot() - saves the current visible page as an image file
- element.screenshot() - captures just a single web element rather than the full page
- Screenshots are typically stored with the test name and timestamp for easy tracking
Understanding Cookies in Automation
Cookies store small pieces of data such as session tokens and login state. Selenium allows scripts to read, add, and delete cookies, which is especially useful for skipping repetitive login steps during testing.
Common Cookie Operations
| Method | Purpose |
|---|---|
| driver.get_cookies() | Returns all cookies for the current domain |
| driver.add_cookie() | Adds a new cookie, such as a saved session token |
| driver.delete_all_cookies() | Clears all cookies, useful for resetting test state |
Bringing It All Together
Screenshots and cookie management round out the essential toolkit for reliable, debuggable Selenium automation - combined with the locators, navigation, and script structure covered earlier, you now have a solid foundation to build real automated test suites.
Ready to master Selenium Training Course?
Join Uncodemy's hands-on training and build real automation skills with expert mentors.