Tests the browser UI. Can not inject user input or depend on focus/activation behavior because it can be run in parallel processes and/or with a locked screen, headless etc. For tests sensitive to that, use interactive_ui_tests. For example, when tests need to navigate to chrome://hang (see chrome/browser/ui/webui/ntp/new_tab_ui_uitest.cc)

cacheinvalidation_unittests

chromedriver_unittests

content_browsertests

Similar to browser_tests, but with a minimal shell contained entirely within content/. This test, as well as the entire content module, has no dependencies on chrome/.

content_gl_tests

content_perftests

content_unittests

courgette_unittests

crypto_unittests

curvecp_unittests

device_unittests

Tests for the device (Bluetooth, HID, USB, etc.) APIs.

ffmpeg_tests

ffmpeg_unittests

gfx_unittests

gpu_tests

interactive_ui_tests

Like browser_tests, but these tests do things like changing window focus, so that the machine running the test can't be used while the test is running. May include browsertests (derived from InProcessBrowserTest) to run in-process in case when the test is sensitive to focus transitions or injects user input/mouse events.

ipc_tests

Tests the IPC subsystem for communication between browser, renderer, and plugin processes.