commit | c9566fe344c0e0c37c22924493e1ed600184532e | [log] [tgz] |
---|---|---|
author | Tommy Nyquist <nyquist@chromium.org> | Mon Oct 09 20:47:09 2017 |
committer | Commit Bot <commit-bot@chromium.org> | Mon Oct 09 20:47:09 2017 |
tree | 77eb1951101c93ff61cf7700c2da0334d6849f08 | |
parent | 6397c59510e8624f906f949d593bc95a4aa9c84c [diff] |
Add documentation regarding field trial test config for in-product help The //components/feature_engagement component is fully configured through Chrome Variations, so it is required to also set up the expected launch configuration in the field trial testing configuration. This is the case for all Chrome Variations experiments, but since the rest of the documentation for feature engagement is very specific, it is easy to forget this part while following the guide. This CL therefore adds it to the required steps and links to the relevant configuration and adds a sample configuration so developers can get a feel for what they are supposed to do. BUG=None Change-Id: I7b50683d803f2d1d646a2632b08dd1e8050408e4 Reviewed-on: https://chromium-review.googlesource.com/707306 Reviewed-by: Theresa <twellington@chromium.org> Commit-Queue: Tommy Nyquist <nyquist@chromium.org> Cr-Commit-Position: refs/heads/master@{#507475}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .