New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 725268 link

Starred by 1 user
Status: Archived
Owner:
█ mtrofin@chromium.org
Last visit > 30 days ago
Closed: Dec 12
Cc:
█ seththompson@chromium.org
█ bradnelson@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Add Response based APIs to WebAssembly shared test suite

Project Member Reported by bradnelson@chromium.org, May 22 2017 
We have LayoutTests for the Response based version of the WebAssembly compileStreaming + instantiateStreaming APIs.
We should cover these in the shared WebAssembly test suite as well:
https://github.com/WebAssembly/testsuite-js

Comment 1 by bradnelson@chromium.org, May 22 2017 

Actually I just realized that these are intented to run headless, so can't really contain the Web embedding.
Please close if this is accurate.

Comment 2 by mtrofin@chromium.org, May 22 2017 

There's an in-browser runner, too. I believe there's a precedent for browser - only tests with IDB, just that we haven't taken a dependency on those tests on the chrome side just yet. So there's work to be done here, indeed.

Comment 3 by foolip@chromium.org, Jun 1 2017 

Should https://github.com/WebAssembly/testsuite-js be merged into web-platform-tests? Splitting the testing across two shared test suites wouldn't be great, and would be the consequence of issue 724151.

Comment 4 by mtrofin@chromium.org, Jun 1 2017 

The way I see it - web assembly is not a web-only technology, so it would be beneficial to continue testing of non-web-specific APIs and functionality separately.

Comment 5 by adamk@chromium.org, Dec 12

Status: Archived (was: Assigned)
►

Sign in to add a comment