126bd9050d
We originally had a `context.Context` for anything that might be traced, but it turned out to be only useful for lifecycle and host functions. For instruction-scoped aspects like memory updates, a context parameter is too fine-grained and also invisible in practice. For example, most users will use the compiler engine, and its memory, global or table access will never use go's context. Signed-off-by: Adrian Cole <adrian@tetrate.io>
This directory contains tests which use multiple packages. For example:
benchcontains benchmark tests.enginecontains variety of end-to-end tests, mainly to ensure the consistency in the behavior between engines.fuzzcasescontains variety of test cases found by the fuzz testing.post1_0contains end-to-end tests for features finished after WebAssembly 1.0 (20191205).spectestcontains end-to-end tests with the WebAssembly specification tests.vstests and benchmarks VS other WebAssembly runtimes.
Note: This doesn't contain WASI tests, as there's not yet an official testsuite. Meanwhile, WASI functions are unit tested including via Text Format imports here