Initial support for unit tests #1403
Open
+79
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Throughout the years, we've written various unit tests, but never took the effort to standardize them.
With the huge refactor in #1391, we decided to implement the TestNG framework which can run these tests automatically.
Use: (subject to change)
... optionally you can click the "Run" button next to execute a singular test directly from within IntelliJ.
Sample output:
This exposes some issues with the codebase which should be addressed before merge:
RawImageTestsfor HTML fail, likely to to slight differences in font rendering between platformsRawImageTestsCPCL tests are failing now.compile-socket,complile-test, and<testng .../>have many redundancies now and should be refactored.testdon't yet leverage the@Testinterface and need to be refactored.compile-socketcreates a redundant copy of our.classfiles inout/qz-tray, which causes confusing when trying to locate the output files. We may want to nuke this redundancy to avoid confusion in the future.