@@ -7,14 +7,14 @@ consists of:
77* A test file that is parsed or compiled (.ts)
88* One or multiple automatically generated fixtures generated from the source file
99
10- Creating a test:
10+ ### Creating a test:
1111
1212* Run ` npm run clean ` to make sure that the sources are tested instead of the distribution
1313* Create a new test file (.ts) within the respective directory (see below) that contains your test code
1414* Follow the instructions below to generate the first fixture(s)
1515* Make sure the fixture(s) contain exactly what you'd expect
1616
17- Updating a test:
17+ ### Updating a test:
1818
1919* Run ` npm run clean ` to make sure that the sources are tested instead of the distribution
2020* Make changes to the respective test file (.ts)
@@ -54,11 +54,11 @@ Note that the parser suite currently can't recreate just a specific fixture.
5454Compiler
5555--------
5656
57- General directory: [ tests/compiler] ( ./compiler )
57+ General directory: [ tests/compiler] ( ./compiler ) < br />
5858Standard library directory: [ tests/compiler/std] ( ./compiler/std )
5959
60- The source file is parsed and compiled to a module, validated, interpreted and the resulting module
61- converted to WebAsssembly text format.
60+ The source file is parsed and compiled to a module, validated and the resulting module converted to
61+ WebAsssembly text format.
6262
6363The text format output is compared to its fixture and the module interpreted in a WebAssembly VM. To
6464assert for runtime conditions, the ` assert ` builtin can be used. Note that tree-shaking is enabled
@@ -94,5 +94,9 @@ $> npm run test:compiler -- testNameWithoutTs --create
9494Other
9595-----
9696
97- Tests in other directories are not run automatically and do not need to be updated. Most of them
98- are legacy tests.
97+ Tests in other directories are not run automatically and do not need to be updated.
98+
99+ * [ tests/allocators] ( ./allocators ) contains the memory allocator test suite
100+ * [ tests/binaryen] ( ./binaryen ) contains various triggers for earlier Binaryen issues
101+ * [ tests/tokenizer] ( ./tokenizer.js ) is a visual test for the tokenizer tokenizing itself
102+ * [ tests/util-path] ( ./util-path.js ) is a sanity test for the path utility
0 commit comments