caraya
caraya copied to clipboard
vipm-io
Assertion and unit test framework for LabVIEW
Once I had the following use case. There was a need to execute unit tests from TestStand. And the idea was not to launch some script/CLI to execute unit tests,...
During our Caraya 1.0 presentation/webinar @JamesMc86 mentioned it would be nice to have the ability to "re-run all tests" from the Results UI. In some cases, this could be possible...
This is more of an "idea exchange" type post with a small PoC. I thought that it might be interesting to be able to work on a VI for your...
Readme file is a bit outdated: functions palette looks different now, example block diagrams contains obsolete functions, two times there is the same button "Install" (but this maybe is done...
Caraya cannot be integrated with automation tools for CI CD until it gets command line interface executable for testing all VIs in a folder and returning jUnit xml into a...
It would be nice to see an indication of the scope of testing in the results window, somehow.  
When you run tests multiple times in a row, via Tools Menu or QuickDrop, a new Caraya results window opens each time the tests are run. This is different than...
The Test Runner classes that run tests from a folder or a project reference are launched by the ACBR (Asynchronous Call By Reference) method through the creation of a virtual...
Caraya's Test Manager (the entity receiving the test results from the Assertion Nodes) doubles down as an Interactive UI. These two functionalities should be decoupled so that the Test Manager's...
Let's eat our own dog food. Now that Caraya supports CLI, it would make sense to build Caraya using its own feature. Implementation should include: - building on CI -...