Step fail Messages with numbering

[aparab]

hi

In case of a step failure (pass /fail  for eg)   I would like to give  number  & then mention the number in a text file  where the  reason & soln will be specified  (similar to labview)

I know the eg for numeric test where it shows the limits & its clear to the operator the  Value is out of limits  but in case of a  pass /fail  its different

pass/fail can have multiple  boolean Inputs with  [AND] [OR] logic. &  therefore its  essential to specify the cause.

is there a  tried tested method to acheive this or I have to make my custom step for the same...

had it been so comfortable if Teststand had also a Failed  status Line  (Failcode, status, source)  on the lines of "error"  ist easy to keep track of events & docementing also

[A_I]

I am not sure I understand entirely but did you consider adding a command in the post expression of the pass/fail test. If you add the following command the user will see the results in the report.

(fail condition 1)? (Step.Result.ReportText = "the reference number you indicated") : (Step.Result.ReportText = "")

(fail condition 2)? (Step.Result.ReportText = "the reference number you indicated") : (Step.Result.ReportText = "")

(fail condition 3)? (Step.Result.ReportText = "the reference number you indicated") : (Step.Result.ReportText = "")

[aparab]

hi Andrew,

Ya tht surely is  one way to do it.

[dug9000]

---

@aparab wrote:

hi

In case of a step failure (pass /fail  for eg)   I would like to give  number  & then mention the number in a text file  where the  reason & soln will be specified  (similar to labview)

I know the eg for numeric test where it shows the limits & its clear to the operator the  Value is out of limits  but in case of a  pass /fail  its different

pass/fail can have multiple  boolean Inputs with  [AND] [OR] logic. &  therefore its  essential to specify the cause.

is there a  tried tested method to acheive this or I have to make my custom step for the same...

had it been so comfortable if Teststand had also a Failed  status Line  (Failcode, status, source)  on the lines of "error"  ist easy to keep track of events & docementing also

---

One idea is, rather than combining a bunch of conditions into one pass/fail step, split out the condition checking into multiple steps. One for each reason you want to give a separate failure description for, and just make the step name indicate the reason for the failure.

You can use none-adapter pass/fail steps for the condition checking if there is only one code module to call to get back multiple booleans.

Hope this helps,

-Doug

[aparab]

thanks Doug,

thts also an approach

i will try it out & hope its scalable.

  hope NI  thinks abt implementing  the same.