NOTE: These directions seem to be incomplete or out of date. On a Linux debug build, UI tests can be run using binaries found at out/Debug/ui_test and out/Debug/ui_unittest. See http://code.google.com/p/chromium/issues/detail?id=95848

Running Chrome UI tests

Our unit tests and ui tests use GTest (http://code.google.com/p/googletest/).

• to run the tests exactly as the buildbot does, use src/chrome/tools/test/smoketests.py (run it using the copy of Python in third_party)
• to run a specific unit/ui test, start the unit_tests/ui_tests project with a command line --gtest_filter=TestGroupName.TestName
• for example: --gtest_filter=IPCMessageTest.Resize
• to run all the tests in a group, use --gtest_filter=Automation*
• to run all the tests with the same name from all groups, use --gtest_filter=*.Crash
• to see all the tests, use --gtest_list_tests

Use the switch --enable-errdialogs to have the target chrome.exe show the kr0m dialog if the target processes hits a DCHECK. Once the dialog is shown you can then attach to the process.

Note that in order to run successfully, the SSL UI tests require you to import the test root CA certificate to your trusted root CA store. The instructions for Windows XP are:

• double-click the test root CA certificate file (http://src.chromium.org/viewvc/chrome/trunk/tools/buildbot/config/slave/cert/), this opens the Certificate Windows dialog
• click Install Certificate
• click Next
• select the option 'Place all certificate in the following store'
• click Browse.., select 'Trusted Root Certificate Authorities', click OK
• click Next and Finish