Issue metadata
Sign in to add a comment
|
testdriver.js duplication |
||||||||||||||||||||||||
Issue descriptionThere was a new file added in wpt similar to testharness. It is called testdriver.js which has a vendor specific part called testdriver-vendor.js. Since we expose Layouttests/resources/*to the tests we need to make sure they are in sync or better just have one copy.
,
Nov 21 2017
robertma@, do you think we should treat this like testharness.js and allow it to go out of sync but bring them back in sync every so often?
,
Nov 21 2017
Yes, we should definitely treat the two JS in the same way. Although we can discuss whether to sync them manually or automatically. The previous decision to sync testharness.js manually is because it can sometimes break in the upstream, and cause a huge (and wrong) rebaseline during import. More human scrutiny is hence needed. (Heard from qyearsley@) However, if the upstream has become more stable (especially if the Travis checks prove to be effective), we can surely revisit the decision.
,
Nov 21 2017
I'll call this a dupe of issue 685854 and update that one. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by nzolghadr@chromium.org
, Nov 3 2017