How to collect custom files

[sai29]

Hello again, I have anither question


I have squash tm with squash autom and i use robort framework, To run my test scenario in execution environment.

So when my test case from robort framework fails i create some other files aprart from .tar file and .xml files which are generated from robot framwork.

How can i make squash tm to collect the custom files generated and display them on the deatils or report in automated suites in squash tm


Thanks in advance

[sai29]

can someone help me on this topic please

[diseaseruthl]

Hey there! Great question — I’ve run into something similar before. By default, Squash TM with Squash AUTOM and Robot Framework mainly pulls in the .xml output for test results, but if you're generating custom files (like logs, screenshots, or debug info), you'll need to tweak your execution environment and post-processing setup. One way is to modify the execution script to move or copy your custom files into the result directory, then reference them via metadata or attach them manually in the Squash TM interface. Another more integrated approach is to extend the XSLT or plugin used to parse Robot’s XML so it includes references to your extra files. It takes a bit of scripting, but it’s doable. Hope that helps a bit!

[sai29]

Hello thanks for the reply,

But i found the way to do it, I edited the provider config in /app/conf for example robotframework.yaml i have added a hooks with after to collect my files with actions/get-files@v4 to collect my custom files.


From this doc:

https://opentestfactory.org/guides/hooks.html

thanks

[ryansmith53]

Thanks for sharing your solution! That’s a really practical approach using hooks and actions/get-files@v4. I think it’s a clean way to make Squash TM collect all the custom files automatically after test execution.
I’ve also tried a similar method in one of my projects: instead of modifying the provider config directly, I created a small wrapper script that moves all the generated custom files into a specific results folder and then references them in the test metadata. It worked pretty well, especially when you have multiple types of custom outputs like logs, screenshots, or debug info.