[Fix: 178] Time attribute should not be serialized as a tag in the JUnit report
[Fix: 177] Correction for the malformed XML Attribute names
[Fix: 169] Test Runner now filters the Excluded VI List when dscovering tests
[Fix: 166] Test Runner linkage info now errors on invalid/broken test during discovery
[Fix: 164] Inverted inputs in Assert Almost Equal are now consistent with other assertions
[Fix: 163] Linkage Info now skips conditionally disabled methods
[Feature: 161] XML JUnit can now be localized (defaults to system's regional settings)
[Fix: 160] Space character in test label now has no impact on result tree location
[Feature: 158] Verbose explanations can now be forced even for tests that assert
[Fix: 155] Conditionally disabled methods do not produce bad linkage in Test Runners
[Feature: 152] Test manager generates event as each individual tests and assertions are processed
[Feature: 151] Verbose explanations can now be added to any assertion
[Feature: 148] Failure descriptions can now be added to any report, including JUnit

Thanks for all the contributions that led to this release, whether by reporting bugs, requesting features that made it to release or by lending a hand in fixing issues or releasing features:

Tanner Blair (@tannerblair)
Sébastien Michaud (@SebMichaud)
Ajay MV (@digiajay)
Pascal Neuperger (@LogMANOriginal)
Francois Normandin (@francois-normandin)
Roberto Olea (@Robbie20)
Hunter Smith (@HunterJKI)
(@phollyni)

francois-normandin was a contributor to this release

[Fix: 178] Time attribute should not be serialized as a tag in the JUnit report
[Fix: 177] Correction for the malformed XML Attribute names
[Fix: 169] Test Runner now filters the Excluded VI List when dscovering tests
[Fix: 166] Test Runner linkage info now errors on invalid/broken test during discovery
[Fix: 164] Inverted inputs in Assert Almost Equal are now consistent with other assertions
[Fix: 163] Linkage Info now skips conditionally disabled methods
[Feature: 161] XML JUnit can now be localized (defaults to system's regional settings)
[Fix: 160] Space character in test label now has no impact on result tree location
[Feature: 158] Verbose explanations can now be forced even for tests that assert
[Fix: 155] Conditionally disabled methods do not produce bad linkage in Test Runners
[Feature: 152] Test manager generates event as each individual tests and assertions are processed
[Feature: 151] Verbose explanations can now be added to any assertion
[Feature: 148] Failure descriptions can now be added to any report, including JUnit

Thanks for all the contributions that led to this release, whether by reporting bugs, requesting features that made it to release or by lending a hand in fixing issues or releasing features:

Tanner Blair (@tannerblair)
Sébastien Michaud (@SebMichaud)
Ajay MV (@digiajay)
Pascal Neuperger (@LogMANOriginal)
Francois Normandin (@francois-normandin)
Roberto Olea (@Robbie20)
Hunter Smith (@HunterJKI)
(@phollyni)

francois-normandin and logmanoriginal were contributors to this release

[Fix: 177] Correction for the malformed XML Attribute names
[Fix: 169] Test Runner now filters the Excluded VI List when dscovering tests
[Fix: 166] Test Runner linkage info now errors on invalid/broken test during discovery
[Fix: 164] Inverted inputs in Assert Almost Equal are now consistent with other assertions
[Fix: 163] Linkage Info now skips conditionally disabled methods
[Feature: 161] XML JUnit can now be localized (defaults to system's regional settings)
[Fix: 160] Space character in test label now has no impact on result tree location
[Feature: 158] Verbose explanations can now be forced even for tests that assert
[Fix: 155] Conditionally disabled methods do not produce bad linkage in Test Runners
[Feature: 152] Test manager generates event as each individual tests and assertions are processed
[Feature: 151] Verbose explanations can now be added to any assertion
[Feature: 148] Failure descriptions can now be added to any report, including JUnit

Thanks for all the contributions that led to this release, whether by reporting bugs, requesting features that made it to release or by lending a hand in fixing issues or releasing features:

Tanner Blair (@tannerblair)
Sébastien Michaud (@SebMichaud)
Ajay MV (@digiajay)
Pascal Neuperger (@LogMANOriginal)
Francois Normandin (@francois-normandin)
Roberto Olea (@Robbie20)
Hunter Smith (@HunterJKI)
(@phollyni)

francois-normandin and logmanoriginal were contributors to this release

[Fix: 169] Test Runner now filters the Excluded VI List when dscovering tests
[Fix: 166] Test Runner linkage info now errors on invalid/broken test during discovery
[Fix: 164] Inverted inputs in Assert Almost Equal are now consistent with other assertions
[Fix: 163] Linkage Info now skips conditionally disabled methods
[Feature: 161] XML JUnit can now be localized (defaults to system's regional settings)
[Fix: 160] Space character in test label now has no impact on result tree location
[Feature: 158] Verbose explanations can now be forced even for tests that assert
[Fix: 155] Conditionally disabled methods do not produce bad linkage in Test Runners
[Feature: 152] Test manager generates event as each individual tests and assertions are processed
[Feature: 151] Verbose explanations can now be added to any assertion
[Feature: 148] Failure descriptions can now be added to any report, including JUnit

Thanks for all the contributions that led to this release, whether by reporting bugs, requesting features that made it to release or by lending a hand in fixing issues or releasing features:

Tanner Blair (@tannerblair)
Sébastien Michaud (@SebMichaud)
Ajay MV (@digiajay)
Francois Normandin (@francois-normandin)
Roberto Olea (@Robbie20)
Hunter Smith (@HunterJKI)
(@phollyni)

francois-normandin was a contributor to this release

[Feature: 152] Publication of Test registration and assertion events when running Test Suite.
[Fix: 156] JUnit Test Report now does not count skipped tests as failures.

Thanks for all the contributions that led to this release, whether by reporting bugs, requesting features that made it to release or by lending a hand in fixing issues or releasing features:

Adam Gluck (@agluck28)
Jörg Hampel (@joerghampel)
Francois Normandin (@francois-normandin)

francois-normandin and joerghampel were contributors to this release

This is a patch to resolve a bug in the application context for running Caraya tests through VI Server. Thanks Pascal Neuperger (@logmanoriginal) for the patches.

Cumulative update 1.2.0 and 1.2.1:
This release includes features to build into PPL, provides Caraya library information and ability to wrap assert methods without redefining the test (as a result, the extension of Caraya Assertion API is now simple and straightforward)

New Features:

[Feature: 112] Added Test Result to the "Run Tests.vi" method.
[Feature: 117] Added ability to wrap test assertions without redefining tests.
[Feature: 121] Expose Caraya Library Information publicly
[Feature: 122] Enabled Ctrl-C to copy test tree results directly from interactive UI
[Feature: 123] Added an example to demonstrate support for specific type assertions

Fixes:

[Issue: 56] Added a geometrically increasing delay on Interactive UI assert result refreshes.
[Fix:120] Run Tests in Active Project is now functionality that is part of Caraya library.
[Fix: 124] Caraya report now does not have duplicated test results after Test Manager uses TestID instead of Call Chain to extract results from datastore.
[Fix: 127] Caraya is now buildable into a PPL directly from the Caraya project.
[Fix: 131] Almost equal now reports a verbose UTF-8 compatible string
[Fix: 133] Handling of linker info errors during test discovery step in Test Runners.
[Fix: 135] Caraya library path now resolves for PPLs, EXE and project-specific installs
[Fix: 137] Fixes the context in which TestRunner is executing
[Fix: 138] Fixes the incorrect re-run of last test in Test Manager UI when no tests found

Thanks for all the contributions that led to this release, whether by reporting bugs, requesting features that made it to release or by lending a hand in fixing issues or releasing features:

Tanner Blair (@tannerblair)
Henrik Dueholm (@HenrikDueholm)
Christopher Field (@volks73)
Andrew Heim (@AndrewHeim)
Jim Kring (@jimkring)
Philip Lundeen (@plundeen)
Stephen Loftus-Mercer (@SRM256)
Blake Mitchell (@bmitc)
Pascal Neuperger (@logmanoriginal)
Francois Normandin (@francois-normandin)
Felipe Pinheiro Silva (@felipefoz)

volks73 , francois-normandin , SRM256 , bmitc , HenrikDueholm , felipefoz , jimkring and phil were contributors to this release

This release includes features to build into PPL, provides Caraya library information and ability to wrap assert methods without redefining the test (as a result, the extension of Caraya Assertion API is now simple and straightforward)

New Features:

[Feature: 112] Added Test Result to the "Run Tests.vi" method.
[Feature: 117] Added ability to wrap test assertions without redefining tests.
[Feature: 121] Expose Caraya Library Information publicly
[Feature: 122] Enabled Ctrl-C to copy test tree results directly from interactive UI
[Feature: 123] Added an example to demonstrate support for specific type assertions

Fixes:

[Issue: 56] Added a geometrically increasing delay on Interactive UI assert result refreshes.
[Fix:120] Run Tests in Active Project is now functionality that is part of Caraya library.
[Fix: 124] Caraya report now does not have duplicated test results after Test Manager uses TestID instead of Call Chain to extract results from datastore.
[Fix: 127] Caraya is now buildable into a PPL directly from the Caraya project.
[Fix: 131] Almost equal now reports a verbose UTF-8 compatible string
[Fix: 133] Handling of linker info errors during test discovery step in Test Runners.
[Fix: 135] Caraya library path now resolves for PPLs, EXE and project-specific installs

Thanks for all the contributions that led to this release, whether by reporting bugs, requesting features that made it to release or by lending a hand in fixing issues or releasing features:

Tanner Blair (@tannerblair)
Henrik Dueholm (@HenrikDueholm)
Christopher Field (@volks73)
Andrew Heim (@AndrewHeim)
Jim Kring (@jimkring)
Philip Lundeen (@plundeen)
Stephen Loftus-Mercer (@SRM256)
Blake Mitchell (@bmitc)
Francois Normandin (@francois-normandin)
Felipe Pinheiro Silva (@felipefoz)

francois-normandin , SRM256 , volks73 , bmitc , HenrikDueholm , felipefoz , jimkring and phil were contributors to this release

Fixes:

[Fix: 98] Fixed the error on re-running tests from the Test Manager when called from "Run Tests in Active Project"
[Fix: 100] Test Event storage now uses Test and Assert IDs to update verbose explanations in reports
[Fix: 101] Broken VIs are now handled properly in the Batch Running all Tests in Active Project
[Fix: 102] Conditionally disable the "UI: Update Count" frame content on RT targets
[Fix: 103] OpenG dependencies are now included in the package (and namespaced)
[Fix: 104] Asserts in SubVIs not appearing as expected in JUnit reports
[Fix: 109] The Test Name/Assert Name are used instead of VI File Name (reverted to same behavior as 1.0.2)
[Fix: 110] Test Event storage now uses Test and Assert IDs to update verbose explanations in reports

New Features:

[Feature: 94] Added a Pre-Build PassFail verification step for package building
[Feature: 95] Test Suite now returns a "Test Result" object when it completes.

Thanks for all the contributions that led to this release, whether by reporting bugs, requesting features that made it to release or by lending a hand in fixing issues or releasing features:

joerghampel , francois-normandin , jimkring , ChrisStrykesAgain , volks73 , JamesMc86 , sas_workshops , SRM256 , jacobson3 and felipefoz were contributors to this release

Fixes:

[Fix: 4] Fixed the intermittent error 1 when destroying Test Suites
[Fix: 34] Added an optional "Execution Time (us)" terminal to assertion methods for reporting
[Fix: 40] Assertions are now sorted in order they occur instead of ascending alphabetically
[Fix: 44] Fixed the conditions that overewrote assertions when test names were identical
[Fix: 47] Double-clicking on assertion result in Test Manager now works after VI has left memory for lvlibs inside lvlibs.
[Fix: 50] Updated the Math Test Suite to use non-deprecated method for Test Report
[Fix: 53] Fixed issues with comparison (greater/less) of variant representations when integers and floats were compared
[Fix: 65] Restored RT compatibility for Process VI after CLI integration
[Fix: 68] Fixed an issue where the number of skipped and failed tests in JUnit report were wrong.
[Fix: 79] Added XML escaping to ensure JUnit parses correctly
[Fix: 92] Upstream error will skip the following tests (Caraya 1.0.0 bug hotfix)

New Features:

[Feature: 34] Time is filtered from the JUnit report if execution time is not provided
[Feature: 41] Upgraded sources to LV2013
[Feature: 43] Added a verbose option the the Test Suite to export detailed explanation of failures
[Feature: 45] Attribute a unique identifier to each assertions performed
[Feature: 48] Added a Rerun All Tests menu in the Test Manager UI.
[Feature: 52] Added support for Command Line Interface which allows discovery and execution of all tests found under a folder. Outputs to a J-Unit compatible report or a plain text report.
[Feature: 55] Creation of a Test Runner class to search and execute tests programmatically. Includes a pre-build action for build integration.
[Feature: 62] Defined error code range (7000-7999) for Caraya framework
[Feature: 64] Support for QuickDrop plugin to run all unit tests in active project (Ctrl-U)
[Feature: 78] Support for nested Test Suites through Test Runner class extensions
[Feature: 87] No Tests Found message added to Test Manager UI when no assertions found
[Feature: 88] Added support for Library Refnum Test Runner

Thanks for all the contributions that led to this release, whether by reporting bugs, requesting features that made it to release or by lending a hand in fixing issues or releasing features:

arjen-hiemstra (@arjen-hiemstra)
Carlo (@carlodri)
Cyril Gambini (@CygaLV)
Matthew Jacobson (@jacobson3)
Sam Kaley (@skaley)
Jim Kring (@jimkring)
Piotr Kruczkowski (@Primary-Key)
laxmanraok (@laxmanraok)
Tomi Maila (@tmaila)
Omar Mussa (@omarmussa)
Francois Normandin (@francois-normandin)
OlivierLabo (@OlivierLabo)
Matt Pollock (@pollockm)
James D. Powell (@drjdpowell)
Chris Stryker (@ChrisStrykesAgain)
Sam Taggart (@stagg54)
Ivan Yakushchenko (@kosist)

Fixes:

[Fix: 4] Fixed the intermittent error 1 when destroying Test Suites
[Fix: 34] Added an optional "Execution Time (us)" terminal to assertion methods for reporting
[Fix: 40] Assertions are now sorted in order they occur instead of ascending alphabetically
[Fix: 44] Fixed the conditions that overewrote assertions when test names were identical
[Fix: 47] Double-clicking on assertion result in Test Manager now works after VI has left memory for lvlibs inside lvlibs.
[Fix: 50] Updated the Math Test Suite to use non-deprecated method for Test Report
[Fix: 53] Fixed issues with comparison (greater/less) of variant representations when integers and floats were compared
[Fix: 65] Restored RT compatibility for Process VI after CLI integration
[Fix: 68] Fixed an issue where the number of skipped and failed tests in JUnit report were wrong.
[Fix: 79] Added XML escaping to ensure JUnit parses correctly

New Features:

[Feature: 34] Time is filtered from the JUnit report if execution time is not provided
[Feature: 41] Upgraded sources to LV2013
[Feature: 43] Added a verbose option the the Test Suite to export detailed explanation of failures
[Feature: 45] Attribute a unique identifier to each assertions performed
[Feature: 48] Added a Rerun All Tests menu in the Test Manager UI.
[Feature: 52] Added support for Command Line Interface which allows discovery and execution of all tests found under a folder. Outputs to a J-Unit compatible report or a plain text report.
[Feature: 55] Creation of a Test Runner class to search and execute tests programmatically. Includes a pre-build action for build integration.
[Feature: 62] Defined error code range (7000-7999) for Caraya framework
[Feature: 64] Support for QuickDrop plugin to run all unit tests in active project (Ctrl-U)
[Feature: 78] Support for nested Test Suites through Test Runner class extensions
[Feature: 87] No Tests Found message added to Test Manager UI when no assertions found
[Feature: 88] Added support for Library Refnum Test Runner

Thanks for all the contributions that led to this release, whether by reporting bugs, requesting features that made it to release or by lending a hand in fixing issues or releasing features:

arjen-hiemstra (@arjen-hiemstra)
Carlo (@carlodri)
Cyril Gambini (@CygaLV)
Matthew Jacobson (@jacobson3)
Sam Kaley (@skaley)
Jim Kring (@jimkring)
Piotr Kruczkowski (@Primary-Key)
laxmanraok (@laxmanraok)
Tomi Maila (@tmaila)
Omar Mussa (@omarmussa)
Francois Normandin (@francois-normandin)
OlivierLabo (@OlivierLabo)
Matt Pollock (@pollockm)
James D. Powell (@drjdpowell)
Chris Stryker (@ChrisStrykesAgain)
Sam Taggart (@stagg54)
Ivan Yakushchenko (@kosist)

Fixes:

[Fix: 4] Fixed the intermittent error 1 when destroying Test Suites
[Fix: 34] Added an optional "Execution Time (us)" terminal to assertion methods for reporting
[Fix: 40] Assertions are now sorted in order they occur instead of ascending alphabetically
[Fix: 44] Fixed the conditions that overewrote assertions when test names were identical
[Fix: 47] Double-clicking on assertion result in Test Manager now works after VI has left memory for lvlibs inside lvlibs.
[Fix: 50] Updated the Math Test Suite to use non-deprecated method for Test Report
[Fix: 53] Fixed issues with comparison (greater/less) of variant representations when integers and floats were compared
[Fix: 65] Restored RT compatibility for Process VI after CLI integration
[Fix: 68] Fixed an issue where the number of skipped and failed tests in JUnit report were wrong.
[Fix: 79] Added XML escaping to ensure JUnit parses correctly

New Features:

[Feature: 34] Time is filtered from the JUnit report if execution time is not provided
[Feature: 41] Upgraded sources to LV2013
[Feature: 43] Added a verbose option the the Test Suite to export detailed explanation of failures
[Feature: 45] Attribute a unique identifier to each assertions performed
[Feature: 48] Added a Rerun All Tests menu in the Test Manager UI.
[Feature: 52] Added support for Command Line Interface which allows discovery and execution of all tests found under a folder. Outputs to a J-Unit compatible report or a plain text report.
[Feature: 55] Creation of a Test Runner class to search and execute tests programmatically. Includes a pre-build action for build integration.
[Feature: 62] Defined error code range (7000-7999) for Caraya framework
[Feature: 64] Support for QuickDrop plugin to run all unit tests in active project (Ctrl-U)
[Feature: 78] Support for nested Test Suites through Test Runner class extensions
[Feature: 87] No Tests Found message added to Test Manager UI when no assertions found

Thanks for all the contributions that led to this release, whether by reporting bugs, requesting features that made it to release or by lending a hand in fixing issues or releasing features:

arjen-hiemstra (@arjen-hiemstra)
Carlo (@carlodri)
Cyril Gambini (@CygaLV)
Matthew Jacobson (@jacobson3)
Sam Kaley (@skaley)
kosist (@kosist)
Jim Kring (@jimkring)
Piotr Kruczkowski (@Primary-Key)
laxmanraok (@laxmanraok)
Tomi Maila (@tmaila)
Omar Mussa (@omarmussa)
Francois Normandin (@francois-normandin)
OlivierLabo (@OlivierLabo)
Matt Pollock (@pollockm)
James D. Powell (@drjdpowell)
Chris Stryker (@ChrisStrykesAgain)
Sam Taggart (@stagg54)

[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.
[Fix: 31] Equal Value Comparison now asserts correctly when comparing equal typedef with non-typedef values
[Fix: 32] Added recursive verification inside cluster to assert value equality for nested values with different type representations
[Feature: 5] Added ability to show only failed tests on the main UI
[Fix: 3] Clicking on expand/collapse (+/-) tree node quickly will no longer open the test VI (as a double-click on test does)

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)

[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.
[Fix: 31] Equal Value Comparison now asserts correctly when comparing equal typedef with non-typedef values
[Fix: 32] Added recursive verification inside cluster to assert value equality for nested values with different type representations

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)

[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.

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)

Updated the documentation.

Added a help file.

Added keyboard shortcut Ctrl+W to close Caraya UI.

No longer returns an error when using empty test suites.

- Open block diagram when results are double clicked

- Added Integer Dictionary example

- New toolkit and palette icon
- Clearer UI to help spot the failed test
- Clearer examples to help new users
- Changed Label input of assert VIs to be recommended instead of optional
- Changed non-palette VIs to be of private scope
- Fixed an issue where an assert in a subVI of a test case incorrectly treated as a test

Improved examples and documentation