UTF-8 report, Test Result update

[Feature: 180] Report Export methods now convert test to UTF-8 before writing to file
[Feature: 184] Allow Test Result's "Add Node" to update if already in variant map
[Feature: 185] Allow DefineTest to register with a caller

Hotfix: Issue 178 -- time attribute serialization in JUnit reports

Hotfix for issue 178. Updated release notes in BOLD

Release Notes:
[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)

Hotfix: XML Attribute Names

Hotfix for issue 177. Updated release notes in BOLD

Release Notes:
[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)

1.4.0

This release introduces a new Test or Assert Property feature that developers can use to add attributes to their individual tests or assertions. The attributes are in the form of key-value pairs and are added to an Extended Test Result cluster to be processed by custom report classes. The feature is optional and accessible through a new Assert/Test method output terminal, as to not have any impact on test execution speeds.

The Test Manager was also modified to use a class-based messaging strategy, as opposed to a variant that can be interpreted based on the name. This feature is to prepare the Test Manager decoupling in future versions, but was also a good opportunity to implement the above-mentioned properties in a more scalable way. The Test and Assert Nodes use extensions to the TestManagerMsg base class to broadcast to the Test Manager. Properties are extensions of this base class as well.

Finally, the Test Manager UI now has a Text-based report view in addition to the customary tree structure. It is an experiment to gather feedback on how Caraya users engage with the UI.

Release Notes:

[Fix: 169] Test Runner now filters the Excluded VI List when discovering 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

###Contributors
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)

Test Registration and Assertion Events

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

After installing the package, run this example code for an example of how to monitor Test Registrations, Assertions and Assertion updates

\examples\JKI\Caraya\suites\Math Test Suite (Result Event).vi

Patch for application context

Cumulative patch for 1.2.0:

[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# What's New in 1.2

Additional Contributor:

• Pascal Neuperger (@logmanoriginal)

(Cumulative release note 1.2.x)
This minor version 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)

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

Fixed Issues (details)

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

Contributors

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)

PPL support and Assert Test Wrapper

What's New in 1.2

This minor version 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)

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

Fixed Issues (details)

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

Contributors

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)

Test Result as returned value of Test Suite destroy method

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.

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 is used instead of VI File Name
[Fix: 110] Test Event storage now uses Test and Assert IDs to update verbose explanations in reports

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:

Christopher Field (@volks73)
Joerg Hampel (@joerghampel)
Matthew Jacobson (@jacobson3)
Jim Kring (@jimkring)
James McNally (@JamesMc86)
Francois Normandin (@francois-normandin)
Felipe Pinheiro Silva (@felipefoz)
Chris Stryker (@ChrisStrykesAgain)
Sam Taggart (@stagg54)
Antonio Terrazas (@aterrazasl)
SRM256 (@SRM256)

Hotfix - Upstream error skips assertions

Cumulative with 1.0 Release Notes:

[Fix: 92] Upstream error will skip the following tests (Caraya 1.0.0 bug hotfix)

Caraya 1.0

Cumulative with 1.0 Release Notes:

[Feature: 88] Added support for Library Refnum Test Runner