stagg54
commented
2 months ago You aren't doing anything wrong. That is exactly what is intended, except that I haven't fully implemented it yet. It is on the roadmap and I haven't gotten around to it yet. I just recently started working on it. Luckily for you I started implementing it in Caraya first.
Try downloading the artifacts from here: https://github.com/approvals/ApprovalTests.LabVIEW/actions/runs/10926173797 They are at the bottom of the page.
Install that package and in the Caraya extension you should see another optional input next to the Options cluster called "Label". Wire that with your test label and you should see the behaviour you are looking for. No need to do all those objects and property nodes.
Let me know if that works for you. If it does, then I'll implement it in the other extensions and make a new release.
phorn-NI
I've got a test that has multiple scenarios to test the vi under test against, and have a different label for each (this was previously a standard Caraya unit test where I built the expected maps on the test block diagram - that was passing so I know the vi is correct currently - I'm planning to remove the timestamp input as that is only there for the test so I can pass in a constant timestamp, I'll remove it and add a scrubber once the test is working).
The VI is called Test LLD Update.vi
So I'd expect there to be 3 approved files created:
But instead I just get Test LLD Update.approved.txt
I can see in a probe that there is 2 places where the Test VI Name and Test Label can be stored in the class - is it going into the correct one? I don't have an accessor to put it into the Namer.lvclass data
Am I doing something wrong?