Re: [presentation-api] [meta] Presentation API Testing

Reporting on what I'm aware of...

I think the coverage document is up-to-date, and we are late on 
enacting the test plan that it contains. Not "very very" late, but 
late nevertheless.

@tomoyukilabs has prepared more complete `getAvailability` tests end 
of November:
https://github.com/w3c/web-platform-tests/pull/4257

Reviewing these tests triggered the issues I raised against the 
Presentation API. These tests were put on hold in the meantime (e.g. 
tests change depending on whether the same Promise is always returned,
 only if unsettled, or something else). I think we'll be done with 
`getAvailability` testing once these tests have been adjusted.

Tests on "reconnect", "close" and "terminate" operations on the 
controlling side could still be improved, but they already check main 
steps there, so we're already in a good shape.

There are a couple of meta-issues to fix and improve existing tests. 
@obstschale is working on that.

Further tests (receiver, messaging) are somewhat blocked by the lack 
of a functional receiver implementation (although there may be one 
with Fennec now, I haven't checked), but also - and mainly? - for lack
 of time available to work on them.

The testing effort could use more resources!




-- 
GitHub Notification of comment by tidoust
Please view or discuss this issue at 
https://github.com/w3c/presentation-api/issues/266#issuecomment-268511589
 using your GitHub account

Received on Wednesday, 21 December 2016 12:30:35 UTC