Using layer based animations in Views can improve performance and reduce jankiness, but they're rather difficult to set up. The AnimationBuilder classes can vastly reduce complexity and improve readability for layer animations. Suppose you needed to

Learn how Chromium developers can reduce the chance of n-day exploitation.

Learn how to work with the code behind Chrome's iOS app.

Learn how Clang's static analysis framework takes over the toil of thread-safety proofs.

The same type may sometimes represent values from incompatible domains, which can cause bugs. Fortunately, Chromium's //base makes it easy to introduce explicit, distinct types.

Implementing a policy enforcement check for Chrome and the infrastructure has enabled us to verify that certain minimum standards for security are met.

Depot Tools is a collection of tools built on top of Git to simplify the workflow of developers contributing to the Chromium codebase and related projects.

Tast is a new UI library has been created that uses the Chrome a11y (accessibility) tree to control the ChromeOS UI. The library enables developers to easily create End-to-end tests against any visible UI surface.

Adding benchmarks is an easy way to prevent performance regressions and help improve performance.

CLion IDE makes it possible to navigate across symbols, search the codebase, and more.

Test coverage measures how much source code is executed when a particular test suite runs.

When writing a browser test, you often want to programmatically perform setup actions that the user could do manually. To help you do this, mixins are a suite of tools for performing non-trivial browser test setup in a reusable way.

Ever wondered how Chrome keeps itself up-to-date on your desktop? Or how updates are served to Chromebooks, Chromecast, or Android?

In Chromium, it's common to find code written for one component that would be useful elsewhere, but might have hidden restrictions. For safety, limit external access to dangerous functionality by restricting target visibility.

Want to detect regressions for your new feature in Chrome? Add your tests to the waterfall, Chrome's continuous build and test infrastructure!

Do you find yourself running the same test over and over in the debugger, trying to figure out how the code got in a bad state? We have a tool for you! RR will record an execution trace, making it easy to step backwards, run backwards, see where variables changed their value or when a function was last called on an object.

Chrome's testing strategy relies heavily on automated functional correctness tests and manual testing, but neither of these reliably catch minor UI regressions. Use pixel tests to automate testing your desktop browser UI.

You may find you are asked to fix high-priority security bugs discovered by ClusterFuzz. What is it? Should you take those bugs seriously? How can you help?

GWP-ASan is a heap-only memory error detector designed to be used in the wild. It detects use-after-frees, buffer overflows/underflows, and double frees. Unlike ASan, it does not detect errors on the stack or in globals.

Compiling a single Chromium source file by hand can help developers experiment with compiler optimization options, understand subtle macro details, or minimize a compiler bug. This month, we take a look at how to preprocess source.

Chrome's issue tracker, Monorail, offers a grid view that allows you to visualize your issues in a Kanban style board. This episode explains how to use the grid mode.

All code has bugs. The Chrome Browser process has no sandbox, meaning those bugs could give malcious code full access to the whole device. This episode explains the dos and don'ts of coding without a sandbox.

Web Platform tests (WPT) are the preferred way to test web-exposed features, as they are shared with other browsers via GitHub. This month, we take a look at WPT best practices.

Tests are critical because they find bugs and regressions, enforce better designs and make code easier to maintain. This month, we take a look at how to conduct thorough tests with Gerrit.

Flaky tests are a common problem in Chrome. They impact the productivity of other developers, and get disabled over time. This month, we take a look at how to fight test flakiness.

The Chrome team is proud to introduce the Chromium Chronicle, a monthly series geared specifically to Chromium developers - the developers who build the browser. This month, we take a look at task scheduling best practices.

Using layer based animations in Views can improve performance and reduce jankiness, but they're rather difficult to set up. The AnimationBuilder classes can vastly reduce complexity and improve readability for layer animations. Suppose you needed to

Learn how Chromium developers can reduce the chance of n-day exploitation.

Learn how to work with the code behind Chrome's iOS app.

Learn how Clang's static analysis framework takes over the toil of thread-safety proofs.

The same type may sometimes represent values from incompatible domains, which can cause bugs. Fortunately, Chromium's //base makes it easy to introduce explicit, distinct types.

Implementing a policy enforcement check for Chrome and the infrastructure has enabled us to verify that certain minimum standards for security are met.

Depot Tools is a collection of tools built on top of Git to simplify the workflow of developers contributing to the Chromium codebase and related projects.

Tast is a new UI library has been created that uses the Chrome a11y (accessibility) tree to control the ChromeOS UI. The library enables developers to easily create End-to-end tests against any visible UI surface.

Adding benchmarks is an easy way to prevent performance regressions and help improve performance.

CLion IDE makes it possible to navigate across symbols, search the codebase, and more.

Test coverage measures how much source code is executed when a particular test suite runs.

When writing a browser test, you often want to programmatically perform setup actions that the user could do manually. To help you do this, mixins are a suite of tools for performing non-trivial browser test setup in a reusable way.

Ever wondered how Chrome keeps itself up-to-date on your desktop? Or how updates are served to Chromebooks, Chromecast, or Android?

In Chromium, it's common to find code written for one component that would be useful elsewhere, but might have hidden restrictions. For safety, limit external access to dangerous functionality by restricting target visibility.

Want to detect regressions for your new feature in Chrome? Add your tests to the waterfall, Chrome's continuous build and test infrastructure!

Do you find yourself running the same test over and over in the debugger, trying to figure out how the code got in a bad state? We have a tool for you! RR will record an execution trace, making it easy to step backwards, run backwards, see where variables changed their value or when a function was last called on an object.

Chrome's testing strategy relies heavily on automated functional correctness tests and manual testing, but neither of these reliably catch minor UI regressions. Use pixel tests to automate testing your desktop browser UI.

You may find you are asked to fix high-priority security bugs discovered by ClusterFuzz. What is it? Should you take those bugs seriously? How can you help?

GWP-ASan is a heap-only memory error detector designed to be used in the wild. It detects use-after-frees, buffer overflows/underflows, and double frees. Unlike ASan, it does not detect errors on the stack or in globals.

Compiling a single Chromium source file by hand can help developers experiment with compiler optimization options, understand subtle macro details, or minimize a compiler bug. This month, we take a look at how to preprocess source.

Chrome's issue tracker, Monorail, offers a grid view that allows you to visualize your issues in a Kanban style board. This episode explains how to use the grid mode.

All code has bugs. The Chrome Browser process has no sandbox, meaning those bugs could give malcious code full access to the whole device. This episode explains the dos and don'ts of coding without a sandbox.

Web Platform tests (WPT) are the preferred way to test web-exposed features, as they are shared with other browsers via GitHub. This month, we take a look at WPT best practices.

Tests are critical because they find bugs and regressions, enforce better designs and make code easier to maintain. This month, we take a look at how to conduct thorough tests with Gerrit.

Flaky tests are a common problem in Chrome. They impact the productivity of other developers, and get disabled over time. This month, we take a look at how to fight test flakiness.

The Chrome team is proud to introduce the Chromium Chronicle, a monthly series geared specifically to Chromium developers - the developers who build the browser. This month, we take a look at task scheduling best practices.