Make --expose-internals-for-testing work in Android content tests |
||
Issue descriptionCurrently, there's no way to read or modify DocumentMarkers in an Android content test. This means that e.g. tests that test spell check features need to actually rely on spell check itself to add spell check markers, which results in flakiness: https://bugs.chromium.org/p/chromium/issues/detail?id=767486 and also, there's no way to test that DocumentMarkers that only result in painting with no other effects (e.g. composition markers) are added properly: https://chromium-review.googlesource.com/c/chromium/src/+/675743#message-fe42b29ea9370f2314e91ecd496cf45688a7076c Currently, some layout tests use --expose-internals-for-testing to expose a JavaScript API for manipulating DocumentMarkers. If we can make this work in content tests, we can use the API there to improve our test reliability and coverage.
,
Oct 2 2017
This actually already works if you add
@CommandLineFlags.Add({"expose-internals-for-testing"})
before the test class. Not sure if this is new with the ContentJUnit4ClassRunner tests or if I just was doing something wrong when I tried before.
|
||
►
Sign in to add a comment |
||
Comment 1 by rlanday@chromium.org
, Sep 21 2017