wasm-bindgen/crates/js-sys/tests/wasm/main.rs

#![cfg(target_arch = "wasm32")]
#![allow(non_snake_case)]

extern crate futures;
extern crate js_sys;
extern crate wasm_bindgen;
extern crate wasm_bindgen_futures;
extern crate wasm_bindgen_test;

pub mod Array;
pub mod ArrayBuffer;
pub mod ArrayIterator;
pub mod Boolean;
pub mod DataView;
pub mod Date;
pub mod Error;
pub mod EvalError;
pub mod Function;
pub mod Generator;
pub mod Intl;
pub mod Iterator;
pub mod JSON;
pub mod JsString;
pub mod Map;
pub mod MapIterator;
pub mod Math;
pub mod Number;
pub mod Object;
pub mod Promise;
pub mod Proxy;
pub mod RangeError;
pub mod ReferenceError;
pub mod Reflect;
pub mod RegExp;
pub mod Set;
pub mod SetIterator;
pub mod Symbol;
pub mod SyntaxError;
pub mod TypeError;
pub mod TypedArray;
pub mod UriError;
pub mod WeakMap;
pub mod WeakSet;
pub mod WebAssembly;
pub mod global_fns;
Add a test harness to directly execute wasm tests (#524) * Add a test harness to directly execute wasm tests This commits adds a few new crates and infrastructure to enable comands like: cargo test --target wasm32-unknown-unknown The intention here is to make it as low-friction as possible to write wasm tests and also have them execute in a reasonable amount of time. Eventually this is also hopefully enough support to do things like headless testing! For now though this is defintely MVP status rather than fully fleshed out. There's some more information at `crates/test/README.md` about how it works and how to use it, but for now this is mainly intended to play around with locally in this repository for our own tests. * Port a numbe of `js-sys` tests to the new test framework This commit ports a number of existing tests for the `js-sys` crate over to the new test framework created in the previous commit, showing off how they can be executed as well as drastictlly simplifying the tests themselves! This is intended to be a proof of concept for now which we can refine over time. This should also show off that it's possible to incrementally move over to the new test framework. 2018-07-20 21:47:49 +03:00			`#![cfg(target_arch = "wasm32")]`
			`#![allow(non_snake_case)]`

Add more WebAssembly bindings 2018-08-15 23:47:49 +03:00			`extern crate futures;`
Add a test harness to directly execute wasm tests (#524) * Add a test harness to directly execute wasm tests This commits adds a few new crates and infrastructure to enable comands like: cargo test --target wasm32-unknown-unknown The intention here is to make it as low-friction as possible to write wasm tests and also have them execute in a reasonable amount of time. Eventually this is also hopefully enough support to do things like headless testing! For now though this is defintely MVP status rather than fully fleshed out. There's some more information at `crates/test/README.md` about how it works and how to use it, but for now this is mainly intended to play around with locally in this repository for our own tests. * Port a numbe of `js-sys` tests to the new test framework This commit ports a number of existing tests for the `js-sys` crate over to the new test framework created in the previous commit, showing off how they can be executed as well as drastictlly simplifying the tests themselves! This is intended to be a proof of concept for now which we can refine over time. This should also show off that it's possible to incrementally move over to the new test framework. 2018-07-20 21:47:49 +03:00			`extern crate js_sys;`
			`extern crate wasm_bindgen;`
Add more WebAssembly bindings 2018-08-15 23:47:49 +03:00			`extern crate wasm_bindgen_futures;`
Add a test harness to directly execute wasm tests (#524) * Add a test harness to directly execute wasm tests This commits adds a few new crates and infrastructure to enable comands like: cargo test --target wasm32-unknown-unknown The intention here is to make it as low-friction as possible to write wasm tests and also have them execute in a reasonable amount of time. Eventually this is also hopefully enough support to do things like headless testing! For now though this is defintely MVP status rather than fully fleshed out. There's some more information at `crates/test/README.md` about how it works and how to use it, but for now this is mainly intended to play around with locally in this repository for our own tests. * Port a numbe of `js-sys` tests to the new test framework This commit ports a number of existing tests for the `js-sys` crate over to the new test framework created in the previous commit, showing off how they can be executed as well as drastictlly simplifying the tests themselves! This is intended to be a proof of concept for now which we can refine over time. This should also show off that it's possible to incrementally move over to the new test framework. 2018-07-20 21:47:49 +03:00			`extern crate wasm_bindgen_test;`

Migrate Array tests to `wasm-bindgen-test` 2018-07-20 21:34:54 +03:00			`pub mod Array;`
Add a test harness to directly execute wasm tests (#524) * Add a test harness to directly execute wasm tests This commits adds a few new crates and infrastructure to enable comands like: cargo test --target wasm32-unknown-unknown The intention here is to make it as low-friction as possible to write wasm tests and also have them execute in a reasonable amount of time. Eventually this is also hopefully enough support to do things like headless testing! For now though this is defintely MVP status rather than fully fleshed out. There's some more information at `crates/test/README.md` about how it works and how to use it, but for now this is mainly intended to play around with locally in this repository for our own tests. * Port a numbe of `js-sys` tests to the new test framework This commit ports a number of existing tests for the `js-sys` crate over to the new test framework created in the previous commit, showing off how they can be executed as well as drastictlly simplifying the tests themselves! This is intended to be a proof of concept for now which we can refine over time. This should also show off that it's possible to incrementally move over to the new test framework. 2018-07-20 21:47:49 +03:00			`pub mod ArrayBuffer;`
			`pub mod ArrayIterator;`
			`pub mod Boolean;`
			`pub mod DataView;`
Port `Date` tests to `wasm` 2018-07-20 22:07:26 +03:00			`pub mod Date;`
Port `Error` tests to `wasm` 2018-07-20 22:21:41 +03:00			`pub mod Error;`
Add support and tests for EvalError 2018-08-10 02:21:06 +03:00			`pub mod EvalError;`
Migrate `Function` tests to `wasm` 2018-07-20 22:43:07 +03:00			`pub mod Function;`
Port `Generator` tests to `wasm` 2018-07-20 22:56:32 +03:00			`pub mod Generator;`
Port `Intl` tests to wasm 2018-07-20 23:00:44 +03:00			`pub mod Intl;`
js-sys: Add `js_sys::try_iter` for iterating over any `JsValue` Fixes #776 2018-09-25 22:30:04 +03:00			`pub mod Iterator;`
Add initial support and tests for JSON 2018-08-10 03:54:13 +03:00			`pub mod JSON;`
cargo +nightly fmt --all Rustfmt all the things! 2018-09-26 18:26:00 +03:00			`pub mod JsString;`
Port `Map` tests to `wasm` 2018-07-20 23:46:22 +03:00			`pub mod Map;`
Port `MapIterator` tests to `wasm` 2018-07-20 23:57:18 +03:00			`pub mod MapIterator;`
Port `Math` tests to `wasm` 2018-07-21 00:21:29 +03:00			`pub mod Math;`
Port `Number` tests to `wasm` 2018-07-21 00:35:44 +03:00			`pub mod Number;`
Port `Object` tests to `wasm` 2018-07-21 01:23:56 +03:00			`pub mod Object;`
feat(extends): extend promise 2018-08-24 02:25:43 +03:00			`pub mod Promise;`
Port `Proxy` tests to `wasm` 2018-07-21 01:35:15 +03:00			`pub mod Proxy;`
js-sys: Add bindings to `RangeError` 2018-08-10 23:03:44 +03:00			`pub mod RangeError;`
js-sys: Add bindings to `ReferenceError` 2018-08-10 23:03:56 +03:00			`pub mod ReferenceError;`
Port `Reflect` tests to `wasm` 2018-07-22 06:07:55 +03:00			`pub mod Reflect;`
Create bindings for RegExp (#580) * Create bindings for RegExp * Address review comments - Split the constructor into two: `new` and `new_regexp`. This way we can write RegExp::new("foo", "g") rather than RegExp::new(&JsValue::from("foo"), "g"). - The js_name for the setter for lastIndex should be `lastIndex` and not `set_lastIndex`. But fixing this causes a panic. Remove the method for now. 2018-07-30 02:13:42 +03:00			`pub mod RegExp;`
Port `Set` tests to `wasm` 2018-07-21 01:44:15 +03:00			`pub mod Set;`
Port `Symbol` and `SetIterator` tests to `wasm` 2018-07-21 02:19:10 +03:00			`pub mod SetIterator;`
			`pub mod Symbol;`
js-sys: Add bindings for `SyntaxError` 2018-08-10 23:42:13 +03:00			`pub mod SyntaxError;`
js-sys: Add bindings for `TypeError` 2018-08-10 23:45:39 +03:00			`pub mod TypeError;`
Port `TypedArray` tests to `wasm` 2018-07-21 02:31:29 +03:00			`pub mod TypedArray;`
js-sys: Add bindings to `URIError` 2018-08-10 23:37:34 +03:00			`pub mod UriError;`
Port `WeakMap` tests to `wasm` 2018-07-21 03:01:26 +03:00			`pub mod WeakMap;`
Port `WeakSet` tests to `wasm` 2018-07-21 03:07:00 +03:00			`pub mod WeakSet;`
Port `WebAssembly` tests to `wasm` 2018-07-21 03:09:50 +03:00			`pub mod WebAssembly;`
cargo +nightly fmt --all Rustfmt all the things! 2018-09-26 18:26:00 +03:00			`pub mod global_fns;`