Teststand 4.1.1 database problem

[Akiel]

I am looking to put the test results from numericlimit and pass/fail tests into the same table. i have each in there own tables but this does not meet my requirements. Could someone suggest a means to do this please? many thanks

[Tom__Sedlack]

Change your pass-fail tests to numeric.  Pass=1, Fail=0.  Set test limits to = 1.

[Akiel]

its possible but I this is a large existing test solution, is it possible inthe configure database to use an 'if' state ment for example :- 

if propertyexist(logging.stepresult.limit.high) then return logging.stepresult.limit high else return '-' 

I know the syntax is is not correct but would the principle work??   Many thanks

 

[SheelaS]

Hi Akiel,

I would like to understand better what you would like to achieve.  Do you mean that you want all your sequence and sub-sequence results in one display table? Rather than a separate table for each subsequence?  Which report type are you using?

Regards,

[Akiel]

I am trying to get all the testresults for each sequence/sub sequence/step that is described in our test procedures into 1 table and in order of execution, I can get each test type into seperate tables, with regards to report type we are currently using ascii but this is far from satisfactory due to the length of the tests   another option we have considered that i am currently looking into is placeing the results into an excel spreadsheet which we then have the tools to insert into a database, obviously directly in would be ideal      many thanks for your reply

[Dennis_Knutson]

Putting test results in the same table is the same schema as came with TestStand 1. You can modify the current schema to do the same thing. It's pretty bad database design though. To view results from multiple tables is just a matter of writing the correct query.

[Scott_Richardson]

Akiel -

Are you using a default NI schema, and if yes, is it based on 2.x-4.0 or 4.1 and later? 

The 2.x-4.0 STEP_PASSFAILE statement logs results for the Pass/Fail Test step type, but really does not log all that much, just Logging.StepResult.PassFail, which affectively becomes the Passed or Failed for the step status. When you configure a statement to log results for more than one step type, you can use the Expected Properites and Precondition fields when configuring a Column/Parameter to determine whether a value is logged. If no value is logged, the database typically defaults to NULL for that value.

Edited: I did not see the subsequent postings. Falling back to a TS 1.x schema definition would be an option. The 1.x schema, basically placed all step results into a single table. The only problem with this design is that you cannot properly log all the unique step properties that are associated with each step type, and you cannot properly log any additional results that may be added to any step (Additional Results is a new feature of TS 4.1).

Message Edited by Scott Richardson on 05-21-2009 12:04 PM