Report teststand

I use the vc6.0 to develope a gui and use API to excute a sequence file.the code is here:
for(.....)
engine->NewExecution(sqfile, sqfile.sequence.name,0,FALSE,0);
In this loop ,I excute a sequence file. but I can't get a report.
who can tell me how I can do to let the application to generate a report. Tell me the detail steps.
my another problem is how to define the report location.
Thanks----hauk

Hi,
I think that you don't use a ProcessModel to run your sequence file.
If you execute your sequence file with an entry point of the Process Model, this entry point collects the results of the execution and calls the TestReport Callback to generate the report.
To execute the sequence file with a ProcessModel, the second parameter of the NewExecution method should be the name of the entry point and the third parameter should be the reference of the ProcessModel.
Hope that helps,
Bruno

Similar Messages

How to edit "Station ID" to "Test Bench ID" name in HTML Report (TestStand 4.2)...?

Hi Folks,
I have regular HTML report from TestStand 4.2; particularly i want to change the header from "Station ID" name to "Test Bench ID" name.
Can anyone help me on this...?
Thanks for your help...!!!
SB_LV

Here are just 3 options:
1- Probably the easiest and best option. Open this file: C:\Program Files\National Instruments\TestStand 4.2\Components\Language\English\ModelStrings.ini. Search for RPT_HEADER_STATION_ID. Replace the Station ID in the quotes with Test Bench ID:. The ModelStrings.ini is a resource strings file that contains a bunch of basically "global values" that TS references.
2- If you don't want to change your resource strings then open this sequence file: C:\Program Files\National Instruments\TestStand 4.2\Components\Models\TestStandModels\reportgen_html.seq. Open the sequence in there titled- AddReportHeader. Find the step named- Add Station ID. It should be a statement step. In the Expression replace ResStr("MODEL", "RPT_HEADER_STATION_ID") with "Test Bench ID:". This directly edits your process model and every sequence ran on the machine will see the change.
3- Add the Modify Report Header callback to your sequence file. In there you will have ot search the Parameters.ReportHeader string for Station ID: and replace it with Test Bench ID. This will not affect the process model.
Hope that helps,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

Generating 2 test reports for the same test - XML and HTML

Hi All,
I have a special test requirement.
Need to generate 2 test reports for the same test. One in HTML and the other in XML format.
Is there any direct method for that?
How it can be implemented?
Thanks in advance.
SajK

Hi SajK,
To accomplish this task, you will need to modify the process model. For example, if you are using the sequential process model, you can concentrate on the TestReport sequence call and the various report related steps in the Single Pass and Test UUTs sequences.
The TestReport sequence (also a callback) relies on Parameters.ReportOptions.Format to decide which of the following sequences to use when generating the report:
<TestStand>\Components\NI\Models\TestStandModels\reportgen_txt.seq
<TestStand>\Components\NI\Models\TestStandModels\reportgen_html.seq
<TestStand>\Components\NI\Models\TestStandModels\reportgen_xml.seq
In your case, instead of choosing one of the sequences, you could hard code it to use both the html and xml sequences. Be aware that for this to work, you must also modify and/or duplicate most of the report related steps in the Single Pass and Test UUTs sequences. For instance, the Set Report Format step becomes unnecessary since you are hard-coding the report format. On the other hand, the Write UUT Report step needs to be duplicated, one step to write to an html file location, and another to write to the xml file location.
Please note that modifying the process mode in this way will deprecate some of the settings in the report options dialog box (such as the report format). For more information on TestStand report generation, please refer to the following DevZone article:
Report Generation Explained
Regards,
Message Edited by James M on 05-29-2007 03:08 PM

Can't write to TestExec.ini

I had made some changes to a 1st level subsequence (one that is called by the main sequence) and ran some test and all was fine. Then I opened another 1st level subsequence to make similar changes. It opened but I got a message stating that TS couldn't write to TestExec.ini. That was because it was not checked out from ClearCase. Why did TS want to update this file at this time?
Inquiring minds want to know.......
Thanks,
jvh

Hi Larui,
When does this error occur? I've found a KB on error code -17205 that might help you out. It's listed below.
Problem
The NI DataFinder is indexing files on my machine (installs with DIAdem or LabVIEW DataFinder Toolkit or DataFinder Server Edition), and I sometimes receive errors -5001 and -17205 when generating XML or ATML reports from TestStand example sequences. I am able to generate HTML and ASCII reports without any errors – what is causing these errors?
Solution
An explanation of the cause of these errors is provided below. This issue (as described below) is fixed in the NI DataFinder 2011 when TestStand 2010 SP1 or newer is installed.
The NI DataFinder periodically indexes files in certain default directories, one of which is the National Instruments Public directory. When the DataFinder attempts to index a file, it grabs exclusive read access to the file such that no other process can read or write to the file.
When generating an XML or ATML report, TestStand obtains and releases write access to the file on multiple occasions when creating the file, writing to the file, adding/removing root tags, etc., and TestStand does not expect other applications to lock the file. By default, TestStand will attempt to generate a report file in the same directory as the sequence file being run.
You may encounter the above mentioned errors if all of the following apply:
You install a DataPlugin for TestStand XML or ATML report files
You generate an XML or ATML report for a TestStand sequence, such as a TestStand example sequence file
DataFinder is configured to index the directory where TestStand generates the report, such as the <TestStand Examples> directory.
To work around this issue, you can manually exclude a directory where TestStand generates reports from NI DataFinder’s list of Search Areas (directories to index).
The Version Selector application installed by TestStand 2010 SP1 automatically configures DataFinder 2011 to exclude files in the <TestStand Public> directory for all version of TestStand installed on a machine. Thus you will not encounter the above mentioned error when running TestStand example sequences if TestStand 2010 SP1 or newer is installed and DataFinder 2011 is indexing files on your machine.
I hope this helps.
Josh L.
Applications Engineer
National Instruments

How can I Generate two different reports from single execution of Test cases in NI teststand

Hi,
My requirement is to generate two different reports from NI teststand. One for the Logging of error descriptions and the other report is by default generated by the Teststand. How can i generate a txt file that contains error descriptions other than that mentioned in the default report?
Solved!
Go to Solution.

Do you need to do that just for these two sequences but not for other sequences? I don't see a problem to use SequenceFilePostStepRuntimeError. Create this callback in both sequence files and configure them to log into the same file. SequenceFilePostStepRuntimeError callback is called after each step of the sequence file if it has runtime error. You can access the calling step error information via RunState.Caller.Step.Result.Error property. Take a look to attached example.
The "other way" is useful if you need to log errors not for every step of the sequence file, but for some of them. This is more complex, because you need to create a custom step types for these steps. For the custom step you can create substeps (post-step in your case) which will be executed every time after step of this type executed. Then, this is you job to determine if error happened in the step, acces to step's error information is via Step.Result.Error property.
Also, be aware that step's post-expression is not executed in case of error in the step.
Sergey Kolbunov
CLA, CTD
Attachments:
SequenceFilePostStepRuntimeError_Demo.seq ‏7 KB

Reporting mechanism on HTML report file, using TestStand 2012 SP1

Hi,
I am using TestStand 2012 SP1, where the reporting mechanism is configured to be in HTML format.
I am not getting the full report of the sequence file which is executed, however I get a part of it printed on the HTML file.
The following are the configured "Report options",
===========
Contents Tab:
===========
Report Format : HTML Document
Default Numeric Format : %$.13f
Include Step Result: Checked
              Result Filtering Expression : Result.Status=="Failed"
              Include Test Limits : Checked
              Include Measurements : Checked
              Include Arrays : Insert Table
              Filter : Include All
Include Execution Times : Checked
On-The-Fly Rporting and Only Display Latest Results : Checked
Select a Report Generator for producing the Report Body : DLL
===========
Report File Pathname Tab:
===========
Generate Report File Path : Checked
       File Name/Directory Options : Specify Report File Path by Expression
       Report File Path (Sequential Model) :
                        StationGlobals.TopLevelReportPath
                        +RunState.ProcessModelClient.AsPropertyObjectFile.DisplayName+"Report_[<FileDate>]<Unique>.<FileExtension>"
Please let me know a solution to this problem.
Thanks,
Dharani

Jason,
Thankyou for replying.
Yes, I need only the steps which had failed to print on the report file.
The problem what I am facing is, if there are 10 failed steps, the report is not printed for all.
Also the order of printing is not correct for the first step and the last step which is printed on the report file.
I had used "Post Expression" for printing data for all the failed steps. Normally these post expressions should be printed beneath the step in the report file.
However,
1) For the first step which is printed on the html file, the post expression gets printed just above the step and also it gets printed beneath the step.
2) For the last step which is printed on the html file, the post expression is not printed beneath the step.
Please let me know if i need to provide some more information.
Thanks,
Dharani

LabVIEW VI with Report Generation Toolkit elements in a TestStand sequence does not run with a LabVIEW 8.5 Run-Time Engine

Hi all,
I am using LabVIEW 8.5.1 and TestStand 4.1. I have done a TestStand sequence with a VI in it, which uses Report Generation Toolkit elements. On my machine I am using LabVIEW and TestStand with a Development System license. On the other machine I am using TestStand with a Base Deployment license and I have chosen the LabVIEW 8.5 Run-Time Engine in the Adapter Configuration. Everything is running well except of this VI with Report Generation Toolkit elements. The error message is showing that the VI is not executable. It works well only after I have installed LabVIEW with an Evaluation license and chosen LabVIEW 8.5 Development System in the Adapter Configuration.
I have found other posts and a document in the KnowledgeBase with a similar problem: http://digital.ni.com/public.nsf/allkb/8A0E6274D9BD7B1986256F62006AD402?OpenDocument But I am not using EXE files in my sequence, so I don't know how to solve mine. Anybody has an idea?
Solved!
Go to Solution.

Hello guys,
thank you very much for your answers!
@Ruediger:
I tried to follow the instruction for Method 2 in the mentioned document: http://digital.ni.com/public.nsf/allkb/F3DC40A6E3F3B25B862570AD005D1D3D?OpenDocument, but the steps on my machine are different starting from step 4. After I click "Continue..." in step 3, I dont get a window, the system just makes a new folder with the same VI.
To be honest, I am new to LabVIEW and have some difficulties at this time. What I understood from your reply is, that I need to make a LLB-File, where the files from Report Generation Toolkit are in!?
@GovBob:
I was following the instruction in the document: http://digital.ni.com/public.nsf/allkb/9E00E7EFE0635E678625734600779EFE, but it wasnt working. Can you please tell me how I can check if the VI Server is installed and running on the machine?
I am using LabVIEW 8.5.1 and TestStand 4.1 on my machine, on the deploy machine there is TestStand 4.1.1. The version of my Report Generation Toolkit is 1.1.2.
Kind regards, Roman

Problem with Report Generation in TestStand 3.0

While using On-the-Fly Test Report Generation capabilities in TestStand 3.0, the PC become very sluggish and occasionally there are error messages containing an error code of -17000 and the statment, "Out of Memory". The error dialog usually appears while attempting to run the "reportgen_html.seq" file. Do you have any suggestions as to how we may correct this problem?

Hi
The test which you trying to run could potentially be leaking memory. I would suggest that you do the following.
1. Run the tests without report generation and result collection. Monitor the memory usage of your test using either taskinfo2000 or PerfMon and monitor your application.
To turn off result collection go the configure-> station options-> general tab -> Check disable result recording for all Sequences.
To turn off report generation -> configure-> report options-> and check disable report generation
If you tests still give a out of memory error then potentially the tests are leaking memory. Also if you see an increase in memory usage when running your tests then you could potentially be leaking memory in the tests
If your application
does not give errors then I would turn on result collection and keep report generation disabled and check if you get errors.
If you get memory errors then you just might need more RAM to store all the results.
If you still do not get any errors then I would turn on report generation and result collection and set the report to txt. If you still do not get any errors.
If you get errors then you might just need more memory to generate the report and display it.
I hope this help
Regards

By default, Teststand will not include the test step result in subsequence, is there any way to include these step result in report?

By default, Teststand will not include the test step result in subsequence, is there any way to include these step results in report?
Thanks
Jacky

Hi,
If your subsequence is in a separate sequencefile, then check the properties of the sequencefile to make sure that the record has not been disabled.
Regards
Ray Farmer
Regards
Ray Farmer

Report multiple failures with TestStand reporting

I'm pretty new to TestStand so please bear with me. I'm using LabView to test a connector on a digital interface board. So I'm reading and writing dig. signals on say 15 pins in a test. I'm using TestStand to run my VI's. When a test fails TestStand seems to only report one measurement at a time. I want all of the pins that failed to show up in the TestStand report in a format like :
InputPin:A1 OutputPin:B1 Expected:0 Read:1
InputPin:a2 outpuPIn:b1 expected:1 read:0
I tried using the ReportText section of the TestData Cluster but I couldn't format it properly. All of the data sort of runs into each other like this
input:a1 output:b1 expect:0 read:1 input:a2 output:b2
the carriage returns I tried to put in were i
gnored.
Does anybody know how I can report a lot of failures in one report. I hope I explained properly.Thanks

Hi,
Find attached an example using the MultipleNumericLimitTest step type.
All it does is use the array found in Locals call Digital as the DataSource for the Limits. You can check this by selecting the step and doing a right mouse click - select Edit Limits. Then select the Data source Tab. I have add 16 Measurements, one for each of the array elements.
This will give a you a result of each element of the array in the report for that step. But by default it will look like:
Measurement[0] (Measurement 0):
Limits:
Low: 0b1
Comparison Type: EQ (==)
Data: 0b0
Status: Failed
To get the format you require will mean modifying the report sequence file.
Hope this helps a bit
Regards
Ray
Farmer
Regards
Ray Farmer
Attachments:
Sequence_File1.seq ‏26 KB

How to generate different report view in teststand for the same execution?

My requirment is to have two different view for the same report that gets generated during one execution using in TestStand OI(CVI)? One view would be summary view (displays only test step types, excluding action step types) and the other view is detail view that displays all the steps that are recorded. Data for all the steps needs to get recorded in database. Any suggestions are helpful!!
CLD,CTD

Hello.
I think you would have to create two separate reports, one as summary report and one as a 'full' report The viewers are just 'viewers' and simply display whatever you set to them.
I had display a text report that was basically a summary report ( failures only ) and then display an HTML report that contained all steps were set to be recorded. This required quite a bit of modifications on both the process model and the operator interface side. The operator interface (in LabVIEW ) had to contain 2 separate UIReportView controls.
Let me know if that is your desired direction and I could point you to some more ideas.
Thanks,
PH

Teststand automatic test report printing using LabView workaround

I tried the LabView workaround for the automatic printing of test reports in TestStand (see email message below).
It will work if I set the URL to a specific HTML TempReport. However, TestStand is configured to generate a unique test report for each UUT. So, in the test report directory there are xml reports and the occasional HTML report, example TestReport_00104.html. Not sure then what to set the URL to?
Note: Your reference number is included in the Subject field of this message. It is very important that you do not remove or modify this reference number, or your message may be returned to you.
Hi Bill,
Thanks you for your reply.
Right ok. Well, if you are interested in the LabVIEW workaround, I can send this to place it in your modified sequential model.
The workaround works as desired. It does it all automatically. I have set it to not prompt the user for the print dialogue but this can be easily changed. Therefore, for any example program in Teststand, if it is based on the modified sequential model, an HTML style report will be printed on the default printer automatically.
It needs to be placed in the following location:
Within the Sequential Model, within 'Single Pass>>Print Report' do the following:
- Replace all the 'Main' steps (Navigate to HTML, Print HTML File & Close IE Browser) with the LabVIEW function call.
- This one function call will do all the steps above at once.
NOTE: In the LabVIEW VI, you will need to select the correct directory where the new html files are being created. Otherwise the print function will not work. This is called URL. Make you sure you have checked this.
For ease of understanding I have included these steps in a word document with screen shots.
As I do not know which version of LabVIEW you might have, I have attached three versions of the .vi file; 2012, 2011 and 2010.
In regards to the mention of Teststand not having built in functionality for automatic printing of reports, unfortunately this is the case.
I hope this will be a sufficient workaround for you.
If you problems implementing this solution, please ask me for further information. However, it should be fairly simple to do.
Just to inform you, I will be out of the office from 12.45pm today for the rest of the week on annual leave.
I will be back in the office on Monday 14th January 2013, should you have any further queries.
Kind Regards,
Dominic Clarke
National Instruments
Applications Engineering
www.ni.com/support
Attachments:
Print HTML file from LabVIEW.zip ‏39 KB

Hi Bill,
I managed to implement this.
In the sequential model I added a LabVIEW action after 'Add Root Tags To XML Report'
As URL I use a sequence local: Locals.ReportFilePath
I points to the ML report in my case and then the VI works fine.
However I'm looking for extra functionality and that is waiting untill printing is completed.
Can you help me on that ?

How can I change the appearance of html report file generated from Teststand to that I change the orientation of the data in the tables?

For instance, I'd like to have the measurement results, limits, and status all on one line in a table.
I am running Teststand 2.0 on Windows 2000.

Hello Joel_IEI,
You can modify each report entry as it is being generated by doing the following steps:
1) In the TestStand Sequence Editor's Report Options, change the Report Generator to "Sequence".
2) In your sequence file, override the ModifyReportEntry callback. In this callback, you can modify or even replace ENTIRELY the default report information TestStand plans to append to the report. You can use Statement steps to modify the contents of Parameters.ReportEntry (the TestStand variable that you will use to do this), or replace the contents entirely!
You can look at the code example Adding Extra Results to a Report Using the Modi
fyReportEntry Callback Sequence for more information.
David Mc.
National Instruments

I am stunned by TestStand suport engineer's answer to my bug report?

Okay, my HTML is bit rusty. here it is.
So, I ran into this problem that when I put a continued inequality expression (a<x<b) in a Pass/Fail step, it will always pass. This is very easy to duplicate, say you have a local varible x = 3, in a Pass/Fail test step's Data Source Expression you put "0<=Locals.x<=2". Then it will always pass when you run it. If you set b to less than 1, say 0.5, then it will always fail. So I reported this as a bug to NI support. Here is what I got for explanation:
NI support/application engineer:
"I was looking into this behavior further and what is actually happening is that for "a<=x<=b", the program is evaluating a<=x, returning 1 if true or 0 if false, and then checking if that 1 or 0 is <=b. This is why a pass was always returned by your code. I still think that recognizing the continued inequality expression would be a good addition to teststand, so i will suggest this change to R&D."
me:
"In that case, it's just simply wrong (as a bug would cause) since it assumes that b is somewhere between 0 and 1. I don't think that TestStand should check the Boolean return value from evaluating a<=x against b, that does not even make sense or someone did not know what he was doing. It should be reported as a bug, not a feature request for future release."
NI support/application engineer:
"I'm sorry that you feel this way, but this syntax would be executed in the same way by any programming language. the <= or < operators are treated like any operator such as * or +, and so this behavior is completely expected by order of operations. just as a*x*b would find a*x, then apply that result to {result}*b, a<x<b calculates the result of a<x (1 or 0) and applies that result to {result}<b. I do understand your frustration, but this is not a bug; it is completely expected behavior. Please let me know if you have any other questions about this issue."
me:
"Do you really want me to spell this out to you?! I would feel embarrassed if I were you. But you insisted, so here it goes.
You are correct that these operators are treated the same in any programming language. Here is where you got lost, read this again - "just as a*x*b would find a*x, then apply that result to {result}*b, a<x<b calculates the result of a<x (1 or 0) and applies that result to {result}<b."
Why in the world that you would substitute variable x with the result from evaluating a<x for the second comparison x<b?
The answer is that "{result}<b is just NOT the same as x<b". Do you see the problem now?
Do you know the difference between a Boolean and an integer? 1 and 0 can be used to present a Boolean, but when you plug it in an integer comparison and it will be used as an integer which throws the whole comparison out of water. I don't think that any other programming language would do that."
NI support/application engineer:
"I am very sorry that you were not satisfied with my explanation of the problem. I understand that this result is not desirable, but the underlying reason is that TestStand does not understand that you are trying to compare a<x and x<b in the same statement. The continued inequality is an implied conjunction of two comparisons, and TestStand (and other programming languages) do not know how to interpret this implication. I realize that this is not intuitive, and though I would agree that a<x<b seems like it would return 1 if x is between a and b and 0 otherwise, this is not a recognized syntax by TestStand and other languages."

Hi CT,
I agree with you completely that this may be undesired behavior depending upon exactly what code is being written. Thanks for bringing to our attention any behavior that seems undesired, we always want to know about these types of things!
I ran the pseudo code "a<x<b" where a, x, and b are numbers in a few different environments:
VB6: This returns true for any x value.
C#: This does not compile, due to a type mismatch.
C++: This returns true for any x value.
C: This returns true for any x value.
LabVIEW: Using comparison functions, this results in a broken wire due to a type mismatch
LabVIEW: Using a MathScript Node, this returns true for any x value.
I would say, generally speaking, it is accepted behavior to
type cast a Boolean result to an integer when the next function
requires integer parameters. In every language, using the logical AND operator, as Jigg suggested, removes any chance of ambiguity between the coder and the compiler.
The good news is that the product suggestion that the support engineer filed on your behalf will still be reviewed by R&D. So, whether this is a bug or a feature request, it will get its due attention.
Message Edited by Evan P. on 10-15-2008 08:25 PM
Evan Prothro
RF Systems Engineer | NI

How to define a new format of report in TestStand?

Hi,
The report autogeneration by TestStand is not suitable to print to my situation.
So I want to define a new format of HTML report by myself. But I do not know how to get a new blank one.
Thank for help.

For a staring point, you should learn how TestStand creates the report at all. Please read this article.
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Report teststand

Similar Messages

Maybe you are looking for