Re: First chrome wpt test added

On Mon, Oct 30, 2017 at 5:48 PM, Raymond Toy <rtoy@google.com> wrote:

> You want to merge these tests back to the mozilla repo? I'm fine with
> that, but we're planning on removing these constant source node tests from
> chrome's tests, if possible.
>

Sorry, what I meant is: "now that your tests are in wpt, they will be run
on gecko automatically, since we run wpt tests".


> One final detail.  As I mentioned, we have a wrapper  (Audit) around
> testharness and I would like to know the way forward?  I would certainly
> prefer all tests to use the wrapper (because the failure messages are quite
> detailed), but we can certainly live with a mixture of testharness test and
> Chrome Audit.  I don't won't to convert our tests to plain testharness test.
>

I think it's fine (and we might use the wrapper as well), but I haven't had
time to have a look, so I don't really know for sure.

Thanks,
Paul.


>
>
>
>> Paul.
>>
>> [0]: https://hg.mozilla.org/mozilla-central/file/tip/testing/web-
>> platform/tests/webaudio/the-audio-api/the-analysernode-interface
>>
>> On Fri, Oct 27, 2017 at 9:28 PM, Raymond Toy <rtoy@google.com> wrote:
>>
>>> We've landed our first chrome wpt test which is for ConstantSourceNode,
>>> because it's relatively self-contained.
>>>
>>> You can see the results at https://wpt.fyi/webaudio/ch
>>> rome/the-constantsourcenode-interface
>>>
>>> As discussed briefly on the teleconf, we do want to move these to the
>>> right place eventually, but to do that we want to coordinate with all the
>>> browser vendors first.
>>>
>>> Thus, we'd like the vendors to take a look at the tests and see what you
>>> think and whether we should move forward with these.  In particular, Chrome
>>> has a wrapper around the wpt test methods to make it easier to write and
>>> more informative when the tests fail.
>>>
>>> The relevant change is https://github.com/w3c/web-
>>> platform-tests/commit/fabf91dc28ca3e2ae83099b6b169fc16ce657b06
>>>
>>
>>
>