Adds a new category to cargo test that checks whether files compile using mir2wasm, but does not bother to run them. In time these should become a superset of, or even equal to, the run-pass tests.
The test runner will automatically skip over any files that contain xfail. This can be used for tests that should pass but we know they won't right now, such as when they rely on a feature that is not yet implemented.
This change also includes some refactoring of the previous compile tests, and modifies mir2wasm to return an exit status that reflects whether compilation succeeded. We should probably just remove the miri-pass tests, but I'm leaving them for now in case they are a useful reference to getting run-pass to work with some kind of interpreter.
brson
commented
8 years ago
Adds a new category to
cargo testthat checks whether files compile usingmir2wasm, but does not bother to run them. In time these should become a superset of, or even equal to, the run-pass tests.The test runner will automatically skip over any files that contain
xfail. This can be used for tests that should pass but we know they won't right now, such as when they rely on a feature that is not yet implemented.This change also includes some refactoring of the previous compile tests, and modifies
mir2wasmto return an exit status that reflects whether compilation succeeded. We should probably just remove the miri-pass tests, but I'm leaving them for now in case they are a useful reference to getting run-pass to work with some kind of interpreter.Issue #15