Where should we put generic baselines for web tests?

[weiz...@google.com]

Having trouble viewing or submitting this form?

Fill out in Google Forms

I've invited you to fill out a form:

Where should we put generic baselines for web tests?

You are receiving this survey because you are a member of chromium-d...@google.com or blin...@chromium.org. Feel free to skip this if you are not familiar with the situation, for example not working on the code. This is different to 'no strong opinion' below. Some background: as part of the work to run WPT tests and legacy web tests in separate steps on the CQ/CI builders, we moved all platform-agnostic baselines to third_party/blink/web_tests/platform/generic. This made it possible for us to specify dependencies in BUILD.gn. Blink engineers have differing opinions on this. Some strongly support the move, while others strongly object to it. This survey is trying to get input from broader audiences and to help us to make better decisions. The related crbug: https://bugs.chromium.org/p/chromium/issues/detail?id=1299834 The email thread in blink-dev: https://groups.google.com/a/chromium.org/g/blink-dev/c/4svjhuokDCY Misc data: we roughly have 2630 generic wpt baselines, and 1348 platform specific wpt baselines. And roughly 18815 generic baselines for legacy tests, and 23618 platform specific baselines for legacy tests.

Where should we put the generic baselines? * All baselines in one central place, which is third_party/blink/web_tests/platform. WPT and legacy web test baselines next to their respective test files. Virtual test baselines in third_pary/blink/web_tests/platform Only WPT baselines next to their respective test files. Virtual and legacy baselines in third_pary/blink/web_tests/platform No strong opinion. (Optional) Share few sentences about your reasoning Never submit passwords through Google Forms. Powered by This form was created inside of Google.com. Google - Privacy & Terms - About Google

Create your own Google Form