Contents

1. 1 Highlighted Child pages
   1. 1.1 Overview
   2. 1.2 Expectations
   3. 1.3 Test Development Infrastructure
   4. 1.4 Inducing a crash
   5. 1.5 Subpages

Chromium development is heavily test driven. In order to maintain a rapid rate of development across multiple platforms and an ever increasing set of features, it is imperative that test suites be updated, maintained, executed, and evolved. Any new features should have test coverage and in addition most changes should have test coverage. As a contributor to Chrome you are expected to write quality tests that provide ample code coverage. As a reviewer you are expected to ask for tests. The Chromium Continuous Integration system is employed to run these tests 24x7.

Expectations

Developers contributing code are expected to run all tests. This is not typically feasible on a single workstation, so try servers are used. When contributing code, consider whether your change has enough testing. If it is a new feature or module, it should almost certainly be accompanied by tests.

• about:crash - will cause a renderer crash.
• about:inducebrowsercrashforrealz - will cause a browser crash.

Subpages