MCP Testing (Incognito Mode)

Incognito mode testing eliminates cache, localStorage, and cookies that can mask bugs. This skill automatically launches Chrome in incognito mode for each test session, ensuring every run starts fresh and old cached code never persists into your verification steps.

Yes. This skill executes a full suite of MCP Chrome DevTools commands—navigate_page, fill_form, click, wait_for, list_network_requests, take_screenshot—within an incognito session, letting you automate login sequences, page transitions, and UI verification without manual browser interaction.

Launch Chrome with --remote-debugging-port=9222 and --incognito flags, establish a remote debugging session, validate incognito state is active, then execute MCP DevTools commands to navigate, inspect elements, monitor network traffic, and capture screenshots with cache-free results.

Deploy a fix, then use incognito-mode automated testing to verify it immediately. This skill launches a clean browser session, logs in, navigates to the affected page, and confirms the fix works—all without cached code or outdated assets masking the real behavior.

Yes. The skill covers element inspection via Chrome DevTools, network request listing, and console monitoring within incognito sessions, giving you full visibility into page behavior, API calls, and errors in a cache-free environment.

This skill validates that incognito mode is active before executing tests. If validation fails, the test halts rather than running with cached data, preventing false passes and ensuring every verification actually tests clean browser state.