fluencelabs/wasm-bindgen
1
0
Fork 0
mirror of https://github.com/fluencelabs/wasm-bindgen synced 2025-06-27 03:31:35 +00:00
Code Issues Projects Releases Wiki Activity
Files
.cargo
crates
backend
cli
cli-support
futures
js-sys
src
tests
wasm
Array.rs
ArrayBuffer.rs
ArrayIterator.rs
Boolean.rs
DataView.rs
Date.rs
Error.rs
EvalError.rs
Function.js
Function.rs
Generator.js
Generator.rs
Intl.rs
JSON.rs
JsString.js
JsString.rs
Map.rs
MapIterator.rs
Math.rs
Number.rs
Object.js
Object.rs
Promise.rs
Proxy.js
Proxy.rs
RangeError.rs
ReferenceError.rs
Reflect.js
Reflect.rs
RegExp.rs
Set.rs
SetIterator.rs
Symbol.js
Symbol.rs
SyntaxError.rs
TypeError.rs
TypedArray.rs
UriError.rs
WeakMap.rs
WeakSet.rs
WebAssembly.js
WebAssembly.rs
global_fns.rs
main.rs
headless.js
headless.rs
CHANGELOG.md
Cargo.toml
README.md
macro
macro-support
shared
test
test-macro
typescript
wasm-interpreter
web-sys
webidl
webidl-tests
examples
guide
releases
src
tests
.appveyor.yml
.gitattributes
.gitignore
.travis.yml
CHANGELOG.md
CONTRIBUTING.md
Cargo.toml
LICENSE-APACHE
LICENSE-MIT
README.md
build.rs
package.json
publish.rs
91eb399f6f587c00bb875b70235f2716dbb6d54b
wasm-bindgen/crates/js-sys/tests/wasm/main.rs

45 lines
814 B
Rust
Raw Normal View History

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 13:47:49 -05:00
#![cfg(target_arch = "wasm32")]
#![allow(non_snake_case)]
Add more WebAssembly bindings
2018-08-15 22:47:49 +02: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 13:47:49 -05:00
extern crate js_sys;
extern crate wasm_bindgen;
Add more WebAssembly bindings
2018-08-15 22:47:49 +02: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 13:47:49 -05:00
extern crate wasm_bindgen_test;
Migrate tests for global functions to `wasm`
2018-07-20 17:45:00 -07:00
pub mod global_fns;
Migrate Array tests to `wasm-bindgen-test`
2018-07-20 11:34:54 -07: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 13:47:49 -05:00
pub mod ArrayBuffer;
pub mod ArrayIterator;
pub mod Boolean;
pub mod DataView;
Port `Date` tests to `wasm`
2018-07-20 12:07:26 -07:00
pub mod Date;
Port `Error` tests to `wasm`
2018-07-20 12:21:41 -07:00
pub mod Error;
Add support and tests for EvalError
2018-08-09 19:21:06 -04:00
pub mod EvalError;
Migrate `Function` tests to `wasm`
2018-07-20 12:43:07 -07:00
pub mod Function;
Port `Generator` tests to `wasm`
2018-07-20 12:56:32 -07:00
pub mod Generator;
Port `Intl` tests to wasm
2018-07-20 13:00:44 -07:00
pub mod Intl;
Port `JsString` tests to `wasm`
2018-07-20 13:35:46 -07:00
pub mod JsString;
Add initial support and tests for JSON
2018-08-09 20:54:13 -04:00
pub mod JSON;
Port `Map` tests to `wasm`
2018-07-20 13:46:22 -07:00
pub mod Map;
Port `MapIterator` tests to `wasm`
2018-07-20 13:57:18 -07:00
pub mod MapIterator;
Port `Math` tests to `wasm`
2018-07-20 14:21:29 -07:00
pub mod Math;
Port `Number` tests to `wasm`
2018-07-20 14:35:44 -07:00
pub mod Number;
Port `Object` tests to `wasm`
2018-07-20 15:23:56 -07:00
pub mod Object;
feat(extends): extend promise
2018-08-24 01:25:43 +02:00
pub mod Promise;
Port `Proxy` tests to `wasm`
2018-07-20 15:35:15 -07:00
pub mod Proxy;
js-sys: Add bindings to `RangeError`
2018-08-10 13:03:44 -07:00
pub mod RangeError;
js-sys: Add bindings to `ReferenceError`
2018-08-10 13:03:56 -07:00
pub mod ReferenceError;
Port `Reflect` tests to `wasm`
2018-07-21 20:07:55 -07: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 01:13:42 +02:00
pub mod RegExp;
Port `Set` tests to `wasm`
2018-07-20 15:44:15 -07:00
pub mod Set;
Port `Symbol` and `SetIterator` tests to `wasm`
2018-07-20 16:19:10 -07:00
pub mod SetIterator;
pub mod Symbol;
js-sys: Add bindings for `SyntaxError`
2018-08-10 13:42:13 -07:00
pub mod SyntaxError;
js-sys: Add bindings for `TypeError`
2018-08-10 13:45:39 -07:00
pub mod TypeError;
Port `TypedArray` tests to `wasm`
2018-07-20 16:31:29 -07:00
pub mod TypedArray;
js-sys: Add bindings to `URIError`
2018-08-10 13:37:34 -07:00
pub mod UriError;
Port `WeakMap` tests to `wasm`
2018-07-20 17:01:26 -07:00
pub mod WeakMap;
Port `WeakSet` tests to `wasm`
2018-07-20 17:07:00 -07:00
pub mod WeakSet;
Port `WebAssembly` tests to `wasm`
2018-07-20 17:09:50 -07:00
pub mod WebAssembly;
Reference in New Issue Copy Permalink