Skip to content

Patch for application context

Compare
Choose a tag to compare
@francois-normandin francois-normandin released this 11 Jul 16:15
· 55 commits to master since this release

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:

(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: