Looking for input/guidance on maintenance of test coverage during long rollout of upcoming feature

[Colin Blundell]

Hi Chrome infra folks,

The Viz team is readying experimenting with the TreesInViz feature on Dev. This is a feature that broadly changes how the compositor operates, and one that we expect to take up to a year if not more to roll out fully.

As part of this, we're preparing to turn this feature on in fieldtrial_testing_config.json. However, this presents us with a tricky question:

We need to start getting CI coverage of the new codepaths as they will continually regress otherwise, but given the broad impact of the feature and the length of time that it will take to roll out, we don't want to lose test coverage of the existing production codepath either. Specifically, layout tests and browsertests meaningfully exercise different codepaths based on whether the feature is enabled.

Do you have any advice as to whether there are previous examples/best practices/feasible approaches to maintaining CI coverage across both codepaths?

Thanks,

Colin

[Andrew Grieve]

@Henrique Nakashima just set up android-10-x86-nofieldtrial-rel to run without fieldtrail_testing_config.json (bug 447426928). It runs android_browsertests, but if you want desktop coverage as well, you could see about changing an existing CQ bot for a no-field-trial variant (that's what Henrique did), or add a new CI bot.

--
You received this message because you are subscribed to the Google Groups "infra-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to infra-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/infra-dev/CAMGE5NEEAAU3-VSiyidLQTWAgGh_%2BRSdxxapRw_xoyM_%2B-6u1g%40mail.gmail.com.

[Colin Blundell]

Thanks, Andrew! As Henrique is OOO: Do you know who he engaged with to determine the plan and work through the execution of it?