run tests on wasm32-unknown-unknown

[gnzlbg]

Closes #79

[gnzlbg]

@alexcrichton this runs the full testsuite on wasm32-unknown-unknown except for the #[should_panic] tests which I have currently disabled.

[gnzlbg]

Having to use the #[wasm_bindgen_macro], pub mod, pub fn, etc. for tests, disable #[should_panic], are the only "issues" i've encountered.

I think we could have a tiny compiler feature(plugin) that replaces #[test] with the appropriate stuff, and that it would be enough to include that for the wasm target in the top-level Cargo.toml.

That would make testing Rust crates for wasm a two-liner change on nightly, instead of something that one has to take care of for every test.

Obviously, the long term solution would be to use a custom test framework.

[gnzlbg]

@alexcrichton

https://travis-ci.org/rust-lang-nursery/packed_simd/jobs/416883709#L1479

{ Error: Cannot find module 'env'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
    at Function.Module._load (internal/modules/cjs/loader.js:507:25)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:20:18)
    at Object.<anonymous> (/checkout/target/wasm32-unknown-unknown/wbg-tmp/wasm-bindgen-test_bg.js:6:18)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3) code: 'MODULE_NOT_FOUND' }

This happens in debug builds. I am trying to run the tests in release mode to see if the issue persists.

[alexcrichton]

While the modules need to be publich (a known bug) you shouldn't need to use pub on the methods themselves

[alexcrichton]

Hm that basically means that there was an unresolved symbol, do you know if the test expect a symbol from libc or a C library or something like that?

[gnzlbg]

Hm that basically means that there was an unresolved symbol, do you know if the test expect a symbol from libc or a C library or something like that?

It fails only in debug mode; in release everything works as expected.