
from chromium24,080
Guides writing end-to-end browser tests for Chrome web applications using WebAppBrowserTestBase, with setup, waiting patterns, and state validation.
Provides step-by-step guidance for authoring browsertests in the chrome/browser/web_applications area. It explains the recommended test base classes, test environment setup (embedded HTTPS test server), waiting and stability best-practices, and how to validate browser and web-app state in end-to-end tests. Concrete C++ examples show install/launch flows and common wait helpers.
Use this when you need to add or update integration-level browser tests for Chrome web applications — for example, validating install flows, UI interactions, manifest-driven updates, or OS integration behavior. It's aimed at Chromium contributors writing IN_PROC_BROWSER_TESTs.
Agents that assist with C++/Chromium development and testing (tools with code editing, build/test runners, and C++ knowledge) such as Codex/Copilot-style code assistants, local CI runners, and developer tooling automation.
This skill has not been reviewed by our automated audit pipeline yet.
NullAway Guidance
Practical guide to resolving NullAway static analysis issues and migrating code to @NullMarked null-safety in Chromium Java code.
Chromium Latency Instrumentation
Surgically injects TRACE_EVENT macros into Chromium C++ files to identify and resolve latency gaps using a self-healing compile loop.