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)