You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current tests test the stl-library, and system/integration test the combined assembler + interpreter. This issue suggests that the assembler and the interpreter need a testing mechanism for themselves. unit-test their functionalities, their features, and their error handling and edge cases.
Compiler-specific & interpreter-specific tests will benefit in the following ways:
Regression Prevention
Bug Detection
Compiler unit tests ideas:
Test macro creation
Test usage of every "rule"
Test bad rules
Assert that weird expressions fail
Assert that names in expressions are only from the expected life-span
Interpreter unit tests ideas:
Test the debugger (with mocks)
Test run errors
Test handling inputs/outputs (maybe the different IODevices.
Test reading bad fjm files
More tests:
Test assemble and run with different memory widths and different fjm versions.
test a simple loop/double-loop program (like print all primes under 100)
The text was updated successfully, but these errors were encountered:
Current tests support:
The current tests test the stl-library, and system/integration test the combined assembler + interpreter. This issue suggests that the assembler and the interpreter need a testing mechanism for themselves. unit-test their functionalities, their features, and their error handling and edge cases.
Compiler-specific & interpreter-specific tests will benefit in the following ways:
Compiler unit tests ideas:
Interpreter unit tests ideas:
IODevice
s.More tests:
The text was updated successfully, but these errors were encountered: