fluencelabs/wasm-bindgen
1
0
Fork 0
mirror of https://github.com/fluencelabs/wasm-bindgen synced 2025-05-05 18:42:16 +00:00
Code Issues Projects Releases Wiki Activity
wasm-bindgen/crates/cli/src/bin/wasm-bindgen-test-runner/index.html

28 lines
821 B
HTML
Raw Normal View History

Start supporting in-browser testing This commit starts to add support for in-browser testing with `wasm-bindgen-test-runner`. The current idea here is that somehow it'll be configured and it'll spawn a little HTTP server serving up files from the filesystem. This has been tested in various ways but isn't hooked up just yet, wanted to make sure this was somewhat standalone! Future support for actually running these tests will be coming in later commits.
2018-07-24 11:27:06 -07:00
<html>
<head>
<meta content="text/html;charset=utf-8" http-equiv="Content-Type"/>
</head>
<body>
<pre id='output'>Loading scripts...</pre>
<script>
const orig_console_log = console.log;
const orig_console_error = console.error;
console.log = function() {
Support asynchronous tests (#600) * Tweak the implementation of heap closures This commit updates the implementation of the `Closure` type to internally store an `Rc` and be suitable for dropping a `Closure` during the execution of the closure. This is currently needed for promises but may be generally useful as well! * Support asynchronous tests This commit adds support for executing tests asynchronously. This is modeled by tests returning a `Future` instead of simply executing inline, and is signified with `#[wasm_bindgen_test(async)]`. Support for this is added through a new `wasm-bindgen-futures` crate which is a binding between the `futures` crate and JS `Promise` objects. Lots more details can be found in the details of the commit, but one of the end results is that the `web-sys` tests are now entirely contained in the same test suite and don't need `npm install` to be run to execute them! * Review tweaks * Add some bindings for `Function.call` to `js_sys` Name them `call0`, `call1`, `call2`, ... for the number of arguments being passed. * Use oneshots channels with `JsFuture` It did indeed clean up the implementation!
2018-08-01 15:52:24 -05:00
if (window.console_log_redirect)
window.console_log_redirect(orig_console_log, arguments);
Start supporting in-browser testing This commit starts to add support for in-browser testing with `wasm-bindgen-test-runner`. The current idea here is that somehow it'll be configured and it'll spawn a little HTTP server serving up files from the filesystem. This has been tested in various ways but isn't hooked up just yet, wanted to make sure this was somewhat standalone! Future support for actually running these tests will be coming in later commits.
2018-07-24 11:27:06 -07:00
else
orig_console_log.apply(this, arguments);
};
console.error = function() {
Support asynchronous tests (#600) * Tweak the implementation of heap closures This commit updates the implementation of the `Closure` type to internally store an `Rc` and be suitable for dropping a `Closure` during the execution of the closure. This is currently needed for promises but may be generally useful as well! * Support asynchronous tests This commit adds support for executing tests asynchronously. This is modeled by tests returning a `Future` instead of simply executing inline, and is signified with `#[wasm_bindgen_test(async)]`. Support for this is added through a new `wasm-bindgen-futures` crate which is a binding between the `futures` crate and JS `Promise` objects. Lots more details can be found in the details of the commit, but one of the end results is that the `web-sys` tests are now entirely contained in the same test suite and don't need `npm install` to be run to execute them! * Review tweaks * Add some bindings for `Function.call` to `js_sys` Name them `call0`, `call1`, `call2`, ... for the number of arguments being passed. * Use oneshots channels with `JsFuture` It did indeed clean up the implementation!
2018-08-01 15:52:24 -05:00
if (window.console_error_redirect)
window.console_error_redirect(orig_console_error, arguments);
Start supporting in-browser testing This commit starts to add support for in-browser testing with `wasm-bindgen-test-runner`. The current idea here is that somehow it'll be configured and it'll spawn a little HTTP server serving up files from the filesystem. This has been tested in various ways but isn't hooked up just yet, wanted to make sure this was somewhat standalone! Future support for actually running these tests will be coming in later commits.
2018-07-24 11:27:06 -07:00
else
orig_console_error.apply(this, arguments);
};
Support asynchronous tests (#600) * Tweak the implementation of heap closures This commit updates the implementation of the `Closure` type to internally store an `Rc` and be suitable for dropping a `Closure` during the execution of the closure. This is currently needed for promises but may be generally useful as well! * Support asynchronous tests This commit adds support for executing tests asynchronously. This is modeled by tests returning a `Future` instead of simply executing inline, and is signified with `#[wasm_bindgen_test(async)]`. Support for this is added through a new `wasm-bindgen-futures` crate which is a binding between the `futures` crate and JS `Promise` objects. Lots more details can be found in the details of the commit, but one of the end results is that the `web-sys` tests are now entirely contained in the same test suite and don't need `npm install` to be run to execute them! * Review tweaks * Add some bindings for `Function.call` to `js_sys` Name them `call0`, `call1`, `call2`, ... for the number of arguments being passed. * Use oneshots channels with `JsFuture` It did indeed clean up the implementation!
2018-08-01 15:52:24 -05:00
window.__wbg_test_invoke = f => f();
Start supporting in-browser testing This commit starts to add support for in-browser testing with `wasm-bindgen-test-runner`. The current idea here is that somehow it'll be configured and it'll spawn a little HTTP server serving up files from the filesystem. This has been tested in various ways but isn't hooked up just yet, wanted to make sure this was somewhat standalone! Future support for actually running these tests will be coming in later commits.
2018-07-24 11:27:06 -07:00
</script>
<script src='run.js' type=module></script>
</body>
</html>
Reference in New Issue Copy Permalink