Release Note
2.0.0
🔄 Break Changes
- Remove deprecated
endTestAPI. - Changed the default value of
isolatedfromtruetofalse. - Remove deprecated
--testcaseCLI option.
🛠️ Improvements
- Introduce new configuration
entryFilesto reach all source code. (#88)
1.4.1
🚀 Highlight Features
- Supported windows officially.
1.4.0
🚀 Highlight Features
- Introduced new features
isolated: falseto significantly reduce test execution time in large projects. (#73) - Introduce setup and teardown API. (#77)
🛠️ Improvements
- Improved the as-test performances.
- Improved the error messages when test case assert failed.
1.3.1
🚀 Highlight Features
- Defined the meanings of the return values in different situations.
0means success.1means test failed.2means invalid AS file.>2means configuration error.
🛠️ Improvements
- Proper handling of situations where AS files are invalid.
1.3.0
🚀 Highlight Features
- Provides more command line options for finer-grained control of test cases.
- Deprecate
--testcase, replace with--testFiles. - Add
--testNamePattern <name pattern regex>. - Add
--onlyFailuresflag to re-run last failed test cases. - Deprecate
endTest().
- Deprecate
- Provides clearer log for user.
- Expose the framework's
logfunction in the configuration file, and the logs redirected to this function will be appended to the final test report. - Support test crashes and provide good call stack information.
- Expose the framework's
🛠️ Improvements
- Code coverage calculation.
- Skip type definitions.
- Treat switch case correctly.
- Reduced test execution time and memory overhead.
🔄 Arch Changes
- During testing, the framework will execute all
testfunctions once, but will not trigger callbacks, thereby collecting all test cases and then executing the test cases in sequence. - Move lots of framework logic from Assemblyscript to Typescript to reduce the WASM linear memory usage and improve the performance.