Provide error logging

[StephenGerads]

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

[ChrisHawk]

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]

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]

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