tree: 8c023261dae2535bcc03d98e20819b8ecb4b41d6 [path history] [tgz]
  1. internal/
  2. public/
  3. BUILD.gn
  4. components_unittests.filter
  5. DEPS
  6. OWNERS
  7. README.md
components/feature_engagement_tracker/README.md

Feature Engagement Tracker

The Feature Engagement Tracker provides a client-side backend for displaying feature enlightenment or in-product help (IPH) with a clean and easy to use API to be consumed by the UI frontend. The backend behaves as a black box and takes input about user behavior. Whenever the frontend gives a trigger signal that in-product help could be displayed, the backend will provide an answer to whether it is appropriate to show it or not.

The frontend only needs to deal with user interactions and how to display the feature enlightenment or in-product help itself.

The backend is feature agnostic and have no special logic for any specific features, but instead provides a generic API.

Testing

To compile and run tests, assuming the product out directory is out/Debug, use:

ninja -C out/Debug components_unittests ;
./out/Debug/components_unittests \
  --test-launcher-filter-file=components/feature_engagement_tracker/components_unittests.filter

When adding new test suites, also remember to add the suite to the filter file: //components/feature_engagement_tracker/components_unittests.filter.