Nano Banana 2

Advanced browser automation requires handling complex scenarios like authentication, file downloads, popup windows, iframes, and canvas interactions. This skill extends basic browser automation with advanced capabilities including session management, download handling, multi-window coordination, iframe navigation, and advanced interaction patterns.

What Is This?

Overview

Nano Banana 2 provides advanced browser automation capabilities beyond basic navigation and clicking. It handles OAuth and cookie-based authentication, file download management with verification, popup window coordination, iframe content interaction, canvas and WebGL manipulation, geolocation and media permissions, browser extension testing, and complex multi-step workflows.

The skill manages browser sessions persisting cookies and localStorage, handles asynchronous operations like downloads completing, coordinates multiple browser windows and tabs, penetrates iframe boundaries safely, and interacts with canvas elements for visual testing.

This enables automation of sophisticated web applications requiring authentication, file handling, cross-origin navigation, and advanced browser APIs that basic automation cannot address.

Who Should Use This

QA engineers testing complex web applications. Automation engineers building sophisticated workflows. Security researchers testing authentication flows. Developers testing browser extensions. Anyone needing advanced browser automation beyond standard click-and-navigate patterns.

Why Use It?

Problems It Solves

Authentication flows require complex OAuth redirects or cookie management. Session persistence handles authentication across automation runs, eliminating the need to re-authenticate before every test execution.

File downloads need verification of completion and content. Download management waits for completion and validates files against expected checksums or data structures.

Modern applications use iframes, popups, and multiple windows. Cross-context coordination handles these scenarios reliably across different browsers and environments.

Canvas and WebGL elements require special interaction approaches. Advanced APIs enable visual element automation and pixel-level comparison testing.

Core Highlights

OAuth and cookie-based authentication. File download management and verification. Popup window and tab coordination. Iframe content interaction. Canvas and WebGL element handling. Geolocation and media permission management. Browser extension testing. Session persistence across runs. Complex multi-step workflow coordination.

How to Use It?

Basic Usage

Configure advanced scenarios including authentication, downloads, or cross-window interactions.

Automate OAuth login flow and maintain session

Download files and verify content integrity

Test application using multiple browser windows

Specific Scenarios

For authentication testing:

Test OAuth flow with various providers

For file handling:

Download reports and validate data accuracy

For complex UIs:

Interact with content inside iframes and popups

Real-World Examples

A SaaS application requires OAuth authentication. Automation handles the redirect flow, captures tokens, persists sessions across test runs, and validates token refresh. Tests run without re-authenticating each time improving efficiency.

A reporting system generates downloadable files. Automation triggers generation, waits for download completion using browser events, validates file content against expected data, and archives files for auditing. File corruption gets detected before users encounter it.

A complex web application uses multiple iframes and popup windows. Tests navigate between contexts seamlessly, interact with iframe content, handle popup dialogs, coordinate data between windows, and verify cross-window communication works correctly.

Advanced Tips

Store sessions securely using encrypted storage for repeated runs. Verify download checksums not just file presence. Handle browser permission prompts programmatically before they block test execution. Use browser contexts for test isolation to prevent state leaking between runs. Test authentication edge cases including expired tokens, revoked access, and forced logout scenarios. Monitor download progress for large files to avoid premature validation. Debug iframe issues using browser DevTools to inspect context boundaries. Implement automatic cleanup routines for downloaded files after each test suite completes.

When to Use It?

Use Cases

OAuth and SSO authentication testing. File download validation and archival. Complex multi-window application testing. Iframe-heavy application automation. Canvas and WebGL visual testing. Browser extension functionality testing. Session persistence across automation runs.

Related Topics

OAuth 2.0 and OpenID Connect flows. Browser cookie and localStorage management. Cross-origin resource sharing (CORS). iframe security and same-origin policy. File system access in browsers. Browser permission APIs. Browser extension manifest V3.

Important Notes

Requirements

Understanding of web authentication flows. Knowledge of browser security models. Familiarity with async JavaScript patterns. Testing environment setup. Credentials for testing authentication. Storage for downloaded files.

Usage Recommendations

Secure authentication credentials properly using environment variables or secrets management tools. Clean up downloaded files after tests. Test across different browsers for compatibility. Handle authentication errors gracefully. Verify file content not just downloads. Test edge cases like expired sessions. Monitor automation for security issues. Document complex workflows clearly.

Limitations

Some authentication methods difficult to automate. Browser security may block certain actions. Download handling OS-dependent. Cross-origin restrictions may apply. Resource intensive for complex scenarios. Debugging advanced scenarios challenging. May require application cooperation.