New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 768607 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Create helper script for running tests for //components/feature_engagement

Project Member Reported by nyquist@chromium.org, Sep 25 2017

Issue description

Chrome Version: M63
OS: All

What steps will reproduce the problem?
(1) Try to run only the tests from //components/feature_engagement
(2) Run something like:
$ ninja -C out/Debug components_unittests ;
  ./out/Debug/components_unittests \
    --test-launcher-filter-file=components/feature_engagement/components_unittests.filter

What is the expected result?
Tests run.

What happens instead?
Tests run... But it was complicated!

What do we want instead?
We should try to generate something like: 
$ out/Debug/bin/run_feature_engagement_tracker_components_unittests

That should invoke the components_unittests with the correct parameters.
 

Sign in to add a comment