Francois Normandin
Francois Normandin
That is the current implementation. Adding G-CLI could be an option for an add-on package that extends Caraya but I think adding the dependency would make the package much less...
@kosist I chose not to include G-CLI as a dependency in this project, However, I've created an extension package to allow the use of G-CLI. This package depends on G-CLI...
**REQUEST FOR COMMENTS** Do we need to extend the CLI support to also be able to run all the tests that are in a project? The workflow would be the...
This is available with pre-release build 72 https://github.com/JKISoftware/Caraya/releases/tag/1.0.0.72. Still missing a tutorial. Keep issue opened until it does.
@ImreSzebelledi , you are not mistaken. I think I had LabVIEW 2013 opened and ran the CLI test in LabVIEW 2019...
We can already rerun tests.  However, the challenge right now is to rerun **and change test configuration**. For example, let's say we would like to rerun the tests, but...
It's called Process.vi. You'll find it under Caraya.lvlib:Basic Test Manager.lvclass namespace.
This feels like a bug. Can you comment whether or not it is impossible to recall it to open from either project or both? Gut feeling: the assertion factory is...
I re-read issue #96 and it seems to be related to the same root cause. Referencing this here for future investigation in context of both reports. (Not marking as duplicate...
It could work, but I think it introduces a few quirks that we'd need to change: - First, you'd lose the ability to organize the test results in categories (Test...