Siva,
There are a few options you should take into consideration before you
change your report layout. Report Options are configurable from
the Configure -> Report Options menu in the TestStand Sequence
Editor. If you are building XML reports, then this will not be a
trivial task because XML reports are based upon XSL stylesheets.
These require a pretty good knowledge of XML and XSL directives before
changing the stylesheet format. If you are using HTML or TXT
reports, then this task becomes less difficult.
You can also determine how reports are generated. Reports are
built in a DLL or Sequence, depending on your confguration in the
Report Options dialog. The DLL calls a function in the
ModelSupport2.dll. This is a CVI project that you can edit and
recompile for your own needs. The project can be found in the
<TestStand>/Components/NI/Models/TestStandModels directory.
Make sure that any changes you make to this file are saved in the
corresponding <TestStand>/Components/User/Models/ directory, so
that you don't overwrite the original dll. The other option is to
call a Sequence that builds a Report. There are 3 sequence files
that are also found in the <TestStandModels> directory.
They are called ReportGen_HTML.seq, ReportGen_TXT.seq, and
ReportGen_XML.seq. You can edit these sequences to change how
your reports are generated.
The DLL function call or Sequence call is implemented from the
TestReports sequence in the Process Model. One or the other
function call is made based on the parameter you set in the Report
Options dialog.
The NumericLimitsTest step type includes variables that are built into
the report (if they are configured to do so from the Report
Options). For instance, the Numeric Limits or Comp (comparison
string) are included in the Report. You can go to the Type
Pallette, and take a look at the NumericLimitTest step type. If
you right click on the Comp variable and choose Properties... ->
Advanced Properties, then you will see advanced properties that can be
set for a variable. The Comp is set to IncludeInReport by
default. This tells the Report Generation to include this value
in the report. Normally these values are built into a table (for
HTML) or include line feeds in between them (for TXT). You can
change how these reports are generated by looking at the above
mentioned sequence calls.
The final option you have, is to post process the Report that is
generated by each UUT. Again, by looking at the TestReport
sequence, the final call in the Sequence is a Statement called
Concatenate Report Header, Body, and Footer. This builds a string
which is used to build the entire report. You can always build a
code module to edit this string and remove key linefeeds or tables that
are produced.
If you have any specific questions on any of this information, please post them here.
Good Luck!
Tyler Tigue
Applications Engineer
National Instruments
