NI TestStand Idea Exchange

About NI TestStand Idea Exchange

Do you have a feature idea for how to improve NI TestStand? Submit and vote on ideas now!

  1. Browse by label or search in the TestStand Idea Exchange to see if your idea has previously been submitted. If your idea exists sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea. Be sure to submit a separate post for each idea. Note: the TestStand Idea Exchange is not the appropriate forum to submit technical support questions.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see implemented!

The TestStand R&D team is committed to reviewing every idea submitted via the TestStand Idea Exchange. However, we cannot guarantee the implementation of any TestStand Idea Exchange submission until further documented.

Top Authors
cancel
Showing results for 
Search instead for 
Did you mean: 
StephenGerads

Provide error logging

Status: Declined

I'm declining this due to lack of community support and the ease of a workaround. Also, a relevant feature was added in 2017 to log any crash info (not exactly the same, but harder to workaround):

https://zone.ni.com/reference/en-XX/help/370052W-01/tshelp/infotopics/2017whatsnew/#Crash

 

Under Station Options, Preferences, add selector for error logging to:

None

Client SequenceFile Directory

Specific directory

 

check box for: one file for each error

 

check boxes for parameters to log:

error time

error code

error message

sequence file

sequence

step

step action

MySocketIndex

 

3 Comments
ChrisHawk
Member

I think this could be achieve by linking TestStand errors with the generation of OutputMessages.  If an OutputMessage was generated for every error then most of the information requested above is already in an OutputMessage.

 

However a feature to TestStand to log OutputMesages to a file would be needed. Maybe even allow the file path to be specified using macros like the report filename expression to allow different files per execution, thread, category,severity, etc if desired.  If feel this option would have the same development effort and provide a full event/error logging capability that could be tailored to suite many applications.

warren_scott
Active Participant

This is really easy to do with a custom result processor that just logs errors.  (starting with TestStand 2012).  Pretty much just a text style report with a custom filter expression.

WireWeaver
Active Participant
Status changed to: Declined

I'm declining this due to lack of community support and the ease of a workaround. Also, a relevant feature was added in 2017 to log any crash info (not exactly the same, but harder to workaround):

https://zone.ni.com/reference/en-XX/help/370052W-01/tshelp/infotopics/2017whatsnew/#Crash

 

https://www.linkedin.com/in/trentweaver