Custom reports for every UUT in Parallel Mode

[rk_tinelli]

Hey everyone,

I'm developing a test sequence to be executed in the parallel model, and every Test Socket has its own sub sequence and set of steps (Socket 1 executes Test1, Socket 2 execute Test2 and so on...)

I configured my Report Options to generate a new UUT report for each UUT and for each Test Socket as well. This works fine but its configured to save in the Client Sequence File Directory, but I need to save the reports for each Test Socket in a custom folder and have custom base name.

This is what is being generated at the moment: 

What I need to do, have a "Reports" folder with the following sub folders:

 

Inside folder "Socket4",for example, I'm supposed to have this:

You can see that the base name is now "Test4_Report" and it's destination is not specific and equal to the other sockets.

Is there any way to set a custom path for every socket and save the reports for every UUT?

Things I tried:

- this link from the NI website, but didn't help for custom folder, only changed the folder where all of them were saved.

- Using the "ReportOptions" callback and call it in my PreUUT, after I identify my test Socket, with the modified the parameters described below but that didn't work

Parameters.ReportOptions.BaseName = FileGlobals.BaseReportName[4],
Parameters.ReportOptions.Directory = FileGlobals.PathSocket[4],
Parameters.ReportOptions.DirectoryType = "SpecificDirectory"

I'm avoiding to have a a VI module to move the report file (after the Report creation) and modify it's name, so it's one less thing to maintain in the overall test machine.

[WireWeaver]

Try using the $(TestSocket) macro and specifying the report path by expression:

https://www.ni.com/docs/en-US/bundle/teststand/page/specify-report-file-path-by-expression.html

This one worked for me in a quick test:

"$(ClientFileDir)\\Socket$(TestSocket)\\$(ClientFileName)_Report[$(FileTime)][$(FileDate)]$(Unique).$(FileExtension)"

Hope this helps!

Trent

[rk_tinelli]

Hey WireWeaver, thanks for the reply.

Sorry, but I used a bad example for the folders name actually, ideally the folders for each socket won't be called "SocketX", X being the test socket number.

The folder are supposed to have custom names like, "Socket1" folder will be called "Image Test", "Socket2" will be called "Eletrical Test" and so on, so basically the folder should have custom names.

I'll give a good read in the link you shared, it's a great start for the customization, thanks for sharing, maybe the answer is in there.