fluencelabs/wasm-bindgen
1
0
Fork 0
mirror of https://github.com/fluencelabs/wasm-bindgen synced 2025-04-02 18:31:05 +00:00
Code Issues Projects Releases Wiki Activity
92dd8e859f
wasm-bindgen/tests/all/main.rs

27 lines
419 B
Rust
Raw Normal View History

tests: Pull the `project()` builder out into its own crate The WebIDL-based -sys crate will also use this, but I want its tests to be a separate suite that we can run separately and in parallel in CI. Therefore, this testing infrastructure code needs to be share-able between them :)
2018-07-05 14:27:26 -07:00
extern crate wasm_bindgen_test_project_builder as project_builder;
Initial commit
2017-12-14 19:31:01 -08:00
Speed up Travis by running Webpack in fewer tests (#381) * Reorganize Travis configuration * Add a `JOB` env var descriptor to all matrix entries. Not used anywhere but is useful when viewing the whole build on Travis's web interface. * Reorganize where builds are located, moving slow builds first and fast ones last. * Change checking the CLI builds from `cargo build` to `cargo check` * Use YAML references to reduce some duplication * Print some more timing statistics for each test * Extract `Project` helper in tests to a module This'll help make it a bit more extensible over time. At the same time the methods are also slightly reorganized to read more clearly from top to bottom. * Migrate all tests away from Webpack Wepback can take a significant amount of time to execute and when it's multiplied by hundreds of tests that adds up really quickly! After investigating Node's `--experimental-modules` option it looks like it's suitable for our use so this switches all tests to using JS files (moving away from TypeScript as well) with `--experimental-modules` with Node. Tests will be selectively re-enabled with webpack and node.js specific output (that doesn't require `--experimental-modules`), coming in later commits. * Restore the node test for node.js output Ensures it's workable as-is * Only generate typescript with webpack * Only read wasm files for webpack * Skip package.json/node_modules for now * Only generate webpack config if needed * Start a dedicated test module for typescript Will hopefully verify the generated Typescript compiles OK. * Remove unneeded `node` method * Fixup some rebase conflicts * Don't run asmjs example on travis * Fixup generator tests * Attempt to fix windows * Comment windows fix * More test fixes * More exclusions * More test fixes * Relax eslint regex Catch mjs modules as well * Fix eslint * Speed up travis on examples slightly
2018-07-04 22:37:09 -05:00
use project_builder::{project, run};
Move all tests to the same suite Nowadays the compile times are mitigated with incremental compilation and otherwise it's much more ergonomic to run only one test if they're all in the same suite.
2018-04-09 15:32:06 -07:00
mod api;
webidl: add initial support for integration tests
2018-06-10 22:59:09 -07:00
mod char;
Move all tests to the same suite Nowadays the compile times are mitigated with incremental compilation and otherwise it's much more ergonomic to run only one test if they're all in the same suite.
2018-04-09 15:32:06 -07:00
mod classes;
mod closures;
rustfmt all the things
2018-06-27 22:42:34 -07:00
mod comments;
Move all tests to the same suite Nowadays the compile times are mitigated with incremental compilation and otherwise it's much more ergonomic to run only one test if they're all in the same suite.
2018-04-09 15:32:06 -07:00
mod dependencies;
mod enums;
mod import_class;
mod imports;
rustfmt all the things
2018-06-27 22:42:34 -07:00
#[cfg(feature = "js_globals")]
mod js_globals;
Move all tests to the same suite Nowadays the compile times are mitigated with incremental compilation and otherwise it's much more ergonomic to run only one test if they're all in the same suite.
2018-04-09 15:32:06 -07:00
mod jsobjects;
mod math;
mod node;
mod non_debug;
webidl: add initial support for integration tests
2018-06-10 22:59:09 -07:00
mod non_wasm;
Move all tests to the same suite Nowadays the compile times are mitigated with incremental compilation and otherwise it's much more ergonomic to run only one test if they're all in the same suite.
2018-04-09 15:32:06 -07:00
mod simple;
mod slice;
mod structural;
Speed up Travis by running Webpack in fewer tests (#381) * Reorganize Travis configuration * Add a `JOB` env var descriptor to all matrix entries. Not used anywhere but is useful when viewing the whole build on Travis's web interface. * Reorganize where builds are located, moving slow builds first and fast ones last. * Change checking the CLI builds from `cargo build` to `cargo check` * Use YAML references to reduce some duplication * Print some more timing statistics for each test * Extract `Project` helper in tests to a module This'll help make it a bit more extensible over time. At the same time the methods are also slightly reorganized to read more clearly from top to bottom. * Migrate all tests away from Webpack Wepback can take a significant amount of time to execute and when it's multiplied by hundreds of tests that adds up really quickly! After investigating Node's `--experimental-modules` option it looks like it's suitable for our use so this switches all tests to using JS files (moving away from TypeScript as well) with `--experimental-modules` with Node. Tests will be selectively re-enabled with webpack and node.js specific output (that doesn't require `--experimental-modules`), coming in later commits. * Restore the node test for node.js output Ensures it's workable as-is * Only generate typescript with webpack * Only read wasm files for webpack * Skip package.json/node_modules for now * Only generate webpack config if needed * Start a dedicated test module for typescript Will hopefully verify the generated Typescript compiles OK. * Remove unneeded `node` method * Fixup some rebase conflicts * Don't run asmjs example on travis * Fixup generator tests * Attempt to fix windows * Comment windows fix * More test fixes * More exclusions * More test fixes * Relax eslint regex Catch mjs modules as well * Fix eslint * Speed up travis on examples slightly
2018-07-04 22:37:09 -05:00
mod typescript;
Map u64/i64 to BigInt in JS This commit is an implementation of mapping u64/i64 to `BigInt` in JS through the unstable BigInt APIs. The BigInt type will ship soon in Chrome and so this commit builds out the necessary support for wasm-bindgen to use it!
2018-05-05 14:10:25 -07:00
mod u64;
use both npm and yarn in ci
2018-06-21 20:35:04 -07:00
mod validate_prt;
Reference in New Issue Copy Permalink