How do I globally log into the database the results of interested step types?

[Scott_Richardson]

Anh -

You might want to turn on Show Hidden Properties in the station options to be able to see the TS property when you are browsing. You might want to place a breakpoint on the step in the model that you added to ensure that it is being called. Can you break on the cleanup group in your client sequence when you run the sequence using the model to determine if the Locals.ResultList[x].Requirements property exists for the steps that you are recording results for? This should allow you to see if the copy of the requirements property is working.

[Anh Doan]

Scott,

I followed your suggestion, and here is the result:

1. I turned on Show Hidden Properties in the station option => I could see the TS property when I am browsing.  I could see "Step.TS.Requirements.Links"

2. I placed a breakpoint on the step in the model that I added.  

3. Since you asked "Can you break on the cleanup group in your client sequence...", I added a simple statement f(x) on the cleanup group in my client sequence, and place a breakpoint at this statement.  I then ran my client sequence.  The run stopped at this breakpoint => I clicked on the icon f(x) on the "Watch Expression" box,  and browsed to Locals.ResultList[x].  I did not see Locals.ResultList[x].Requirements exists.   

        I then clicked "Step over", and click "Resume All" => the run ran and displayed the report.  The run never stopped at the breakpoint that I placed on the step in the model that I added as I described in #2. above.

        I looked into the database.  The step_result table has only one record for the Main Sequence. No record for the NUmeric Limit Test step that has the requirement.

Did I follow your suggestion correctly?   What should I do next?

Thanks a lot, Scott!

Anh

[Scott_Richardson]

Anh -

Sorry for the delay. Typically the Single Pass and Test UUTs sequences have a step called "Setup Result Settings" that calls the "Setup Result Settings" sequence in ModelSupport.seq. I think you need to step through your model to find out why you are not running the step.