Caraya 0.6.0 Release Notes

What's New

Easier to use Assert function

Now, there's a single PolyVI for Assert that shows a menu of available options. This can easily be quick-dropped as "Assert". And, for those who want to use the palettes, you can still find all the specific instances of Assert under the Assert Functions palette.

Custom test reports (e.g. JUnit)

Now, the Test Suite function allows you to pass in a custom Test Report class that allows you to format your test results any way you choose. And, we've even included a very simple JUnit test report, so you can see how this work. To create your own test report, goto the Tools Menu and select Tools >> Caraya >> Create Test Report From Template... See here for more details on how to create your own test report format.

Run Caraya in a Deployed Executable (Built EXE)

Now, it's possible to include and run Caraya tests inside a deployed (built) executable (EXE) application. This opens up a lot of possibilities for testing functionality inside of deployed applications. See here for more details.

Equality Comparison by Value, Value and Type, or Type

Previously, the Equality Comparison was by Value and Type, which meant that (for example) comparing a U32 and I32 would fail, regardless if they had the same numeric value. Now, there are separate functions that allow comparing equality by Value, Value and Type, or Type.

Almost Equal Comparison of Floating Points

Now, there's a function called Almost Equal, which allows specifying a tolerance (absolute or percentage) for equality comparisons. This is very helpful for some floating point comparisons.

Double clicking on Test Result Highlights Specific Assertion

Double clicking on a test result (in the UI) will highlight the specific Assert function for that test result. Previously, it simply opened the VI that contained the assertion, which could have multiple assert functions being called. This helps the developer hone in on which test failed, when navigating from the results UI.

Minor Fixes

We've fixed some minor issues in the UI where sometimes an error dialog might occur.

Details

• [Feature: #7] Adding support for JUnit-compatible XML file export
• [Feature: #11] Adding an "Assert Equal_Float" assertion to compare float representation within a certain precision
• [Feature: #14] Hook to inject an alternate "Export" format
• [Fix: #15] Running Caraya Assertions in EXE builds
• [Feature: #20] Double-click on test result in Test Manager GUI now points to the Assertion node if Text of label attached to assertion node matches the exact name of the test.
• [Fix: #24] Default report generation now fixes hierarchy of assertions
• [Feature: #25] Change of specification for Assert Equal to separate "Value" and "Value and Type" assertions
• [Feature: #26] Assertions are now grouped in a polymorphic VIfor palette menu.
• [Fix: #27] Double-clicking on empty space in the tree of the Test Manager UI no longer generates an error.
• [Fix: #28] Fixed the issue where opening a test VI after it had left memory would give an error.

Contributors

Thanks to the community members for their issue reports, feature requests and/or code contributions for this release:

• Christopher Field (@volks73)
• Stefan Droege (@StefanD986)
• Kosist (@kosist)
• Francois Normandin (@francois-normandin)
• Omar Mussa (@omarmussa)
• Jim Kring (@jimkring)
• OlivierLabo (@OlivierLabo)
• James Powell (@drjdpowell)
• Neil Pate (@neilpate)