Integrity v0.13.0 comes with the following major changes from its predecessor, 0.12.x:
- When performing tests on maps or objects, Integrity is now able to visualize the exact keys/attributes which caused the comparison to fail. Hugely useful when dealing with larger data sets! The result looks like this:
- The validation now catches repeated usage of the same fixture parameters
- A new "jump to errors" button was added in the Eclipse Test Control view which allows...well...to jump directly to errors ;-)
- Suites with parameters now allow direct usage of (custom/standard) operations when they are called
- Variables and constants now support the declaration of multiple values (comma-separated), just like it has been supported forever for test/call parameters
- The Integrity Test Control view in Eclipse now supports a live display of the number of successful/failed/exception tests while a test is running
- You can now directly jump to lines of tabletests by double-clicking them in the Integrity Test Control view
- The file encoding for Integrity script files can now be specified separately from the systems' default encoding by using the system property "integrity.script.encoding"
- The exit codes returned by the Console Test Executor when exiting have been straightened out. It now returns code 0 on success, code 1 on a parameter error preventing the test from starting, and code 2 when encountering a runtime error during testing that aborted the test.
- A "zombie thread detection" feature has been added to the Console Test Executor: non-daemon threads that are being started during the test execution, but have not ended when the test script execution has finished, are logged on the console now in a warning. Such threads should not exist - if someone triggers the creation of new threads during test runtime, these threads should be shut down during test runtime as well.