NI TestStand Idea Exchange

Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

When a 2d array is added to the report as table, you get the following table:

 

 

[0][0]  00

[0][1]  01

[1][0]  10

[1][1]  01

 

It would be better to have a table like this:

      [0] [1]

[0]  00  10

[1]  10  11

 

Currently this needs to be implememented in the stylesheet. But for a lot of users, this is a complex workaround.

 

 

 

I've encountered on several occassions, customers who assign serial numbers / partnumbers during the test process who still wish to do on-the-fly recording.... and are disatisfied with the default behavior of the reporting because their header persists in showing the blanks etc.

 

While I understand that it's easier to build file paths / headers once, and then append the body content onto them, it would be especially elegant, if there was:

 

(a) a way for me to manually trigger (via a callback perhaps) a refresh of the entire header or

(b) if at the very least, the header section & file path were overwritten/updated once at the very end.

 

Since it seems to me that the header has to be re-written at least partially to account for the failure-chain logic, it wouldn't seem that much more work (or that much more inefficient) to just refresh the whole thing?

The Additional Results Step property is a great way to add customized results to the TestStand report for a particular step without much effort required.  However, there should be an equally simple way to add additional results too all of the steps in a sequence.  The current options are all lacking:

 

  1. Create a SequenceFilePostStep engine callback to manually append results to the result list - this feels hacky
  2. Add additional results to each step - this is tedious
  3. Create custom step types - this is also tedious, as a new step type would be required for each step

I think there should be an additional results option available in either the report options or in the sequence file properties window or the report options window.  Configuring the results here would be identical to adding the additional result to every step in the sequence.

 

Potential implementation of button on report options window:

tsgar.png

 

Additional results button launches a dialog:

ardialog.png

 

something Kekin proposed with the digital signature made me think, that it'd be nice if there was a  means to suppliment/append to header/footer of reports in general without having to do it with raw statement steps...  (and if this already exists I apologize for not checking first).

 

I think it'd be neat if there was an approach similar to the 'Additional Results' logic per step that's available.  In the 'ModifyReportHeader' callback, or in the report options somewhere, a user would be able to supply the data within a certain list of available options/allowable types, and the report generator/DLL would handle the formatting/whitespace such that it works for txt/html/xml headers without the user having to do the formatting themselves.  From my experience, most items added to headers consist of (1) supplimental string data, (2) supplimental numeric data (3) small images/logos(in the case of txt, maybe the alt text can be used, or just the path put into the file...?) 

 

22449i9B8276AA25BFE2CA

 

even if the new info was just tucked into the list/table before the failure chain block, it would be a nice time-saver for users who want a generic report but just have one more UUT detail that needs to show up in the header.

 

Since reports are to certify the test results, it would be nice to have DIGITAL SIGNATURE option to give it FORMAL touch.

It will also help in organizations to authenticate the result.

 

It will be also nice to add some PPT or PHOTOS to report to describe the test setup & UUT.

It'd be neat, in the scenario when a parallel thread is called, if there was some smooth way of gathering the results back into the main thread of the execution for the sake of the report. 

 

I've handled this historically by passing a parameter into the subsequence/thread with the ResultList-index of the parent-step, and then doing some notification based handshaking during cleanup of both threads to quickly copy the Result container out of the sub and back to the parent via API calls. But I bet the R&D types could do this far slicker and reduce the whole thing to a checkbox... 😉

 

21413i267B71BB01EB46E5

 

When I create reports they usually look like:

21417iA1EFA6BABE8471F4

 

I just think it'd be a simple feature to add for users who might be uncomfortable with the API  & ResultList? (Naturally if the sequence doesn't wait at the end it may never be safe to 'pass back' results. But if you're already killing time on the back stretch, why not copy the block up?

 

Cheers,

 

Elaine

Even though we already have an About box for TestStand, it would also be nice to have one for the active TestSequence file as well. The Help menu would have a new item called "About MySequenceFile ...".

 

MySequenceFile About box splash screen:

19679i37712516107E8A41

 

The information in this screen should be loaded directly from a single FileGlobal string whenever a sequence file is made active. This can probably be done already by those that know how, but it should be already part of TestStand by default.

 

 

Eugene

Almost all of our analog measurements are specified in %: example

 

a Power Supply DMM measurement limit is 24.00Vdc +/- 5%

 

We typically have 100+ measurements like this in a project

 

 

Why not include it in the default step types as an optional selection?

I sure would use it, so would my team.

 

I agree that it should not alter existing programs using the default step, but I believe that this feature should have been in Teststand when it was first released.

 

I have run across this in both analog measurements, and the results from an ADC

Think a limit of 0x234 +3%, -7%