WASM Internals 2: Unit testing
Last updated
Last updated
How can webassembly modules be tested?
Which frameworks exist to test webassembly?
Is there any interoperability with the testing frameworks already built for Javascript?
As the purpose of this chapter is to illustrate how to test webassembly code, the first part addresses which dependencies need to be added. These new dependencies won't be anything else than the chosen javascript test framework. In this chapter jest will be placed as the best candidate.
Once all the configuration is completed, it's the moment to start creating the unit tests. For the sake of simplicity and cohesion with the previous part, the testing will target the square function.
NOTE: This second part uses the code already introduced in the first chapter, as it will be necessary for the purposes of the explanation.
The type must indicate that it's a module. Thus it can recognize ES6 modules. If needed, additional information about using ES6 Javascript modules can be found at the end of the chapter. Once this specification is done, the desired module can be executed using Node.js.
File: package.json
Now, the unit tests can be created and run using any common javascript testing framework, usually used for Node.js ordinary modules without any webassembly. To do so, a javascript testing framework will be needed. For the sake of robustness and simplicity, jest (powered by Facebook) is the alternative chosen. But take into account that any other framework would be valid. In an industrial ecosystem this decision would be done according to the characteristics of the company.
The procedure looks as follows:
Install Jest using yarn:
Or npm:
In both cases, the flag dev-dependecy. It's purpose is to act as a dev dependency rather than a production dependency.
Note: Jest documentation uses yarn commands, but npm will also work. You can compare yarn and npm commands in the yarn docs, here.
Then add jest to the package.json. More precisely to it's test variable. An example of the final form of the file would be:
File: package.json
All the tests created for this project will be under the test directory. In order to let jest address the location of the test created, they need to be named with the following pattern:
In this case, a file named math.test.js is created to contain the unit tests.
In the creation of the unit case appears a lot of similarities with the code inhabiting index.js. The main differences are:
Import statements: Because jest struggles dealing with ES6 modules, the old common import statements, from ES5 and below, are going to be used.
NOTE: There is a beta support for ES6 modules going on inside jest. But here those considerations are omited.
Load the desired webassembly module: Before even attempting to test the targeted webassembly module, it needs to be loaded. To do this, the function beforeAll from jest will be used. It's going to be declared as an async function.
NOTE: The math variable is declared as global, so it can be accessed anywhere in the code and its scope is not limited to just being accessed inside beforeAll.
The final assertion using the jest syntax and calling mechanics:
e.g:
It's expected that given the square function and 2 as its input argument, the computed output would be 4.
To run the entire set of test for the given project:
example output:
