From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
06-12-2019 09:09 AM
Hi All,
I have requirement to repeat the complete sequence if any test-case is failed in that sequence . For this , I m configuring the Looping option in sequence model "Main Sequence Callback".Also i m using NI_SimpleTextReport_LabVIEW for report Generation. How can i configure it to Generate the Report each time the main sequence is iterating.
Should I add a condition to repeat the sequence in the sequentialmodel.seq?
06-12-2019 11:00 AM
Trying to understand your requirements:
If test fails then retry entire test from the beginning?
How many times should it retry before finally giving up?
Every time it retries then create a different report? Or do you want to append passed runs with previous failed runs?
I think there is a way to do what you need without modifying the sequentialmodel.seq. Help me understand your requirements better so I can direct you to the correct solution.
Cheers,
06-12-2019 01:44 PM - edited 06-12-2019 01:48 PM
Hi,
1. Yes it will retry from beginning
2. No of retry is configurable through station global
3.Yes I need to create different Report for each iteration
Currently I modified the sequential model ,added a for loop to handle this . It’s working .
please let me know if there is any better way to handle this.
06-13-2019 01:33 PM
If it is working then you probably want to leave it alone.
If it were my choice I would not have modified the process model but used callbacks to accomplish the task. For instance, inside of PreUUT you could have put some logic to repeat the test if it failed. This is assuming you were using the Test UUTs entry point of course. The problem with changing the process model is that now any test you run with that model is stuck to your logic. Also, it is a separate piece of code you have to maintain and worry about.