[Feature request] Visibility of UPLOAD input in the report

[olw-medcom]

Hey there,

I'm noticing that when I have a testcase with an UPLOAD request type, where I expect the user to upload a screenshot, it is not visible in the pdf report? It just says [File content]. Would it be possible to render the screenshots in the report`?

[olw-medcom]

[costas80]

Hi @olw-medcom.

These [File content] entries are added in PDF reports for all cases of file data (images but also any other kinds of files). We explicitly removed files from PDF reports (they used to be included quite some time ago) because we could not ensure they would render correctly (even for text-based files) and also because reports could end up getting huge.

In the case of images, the issue is even more tricky as these could furthermore be unsafe to render (e.g. when handling SVGs). Also, images that are not sized accordingly will not display if they exceed boundaries, an issue that we can't address simply with CSS limitations (the PDF rendering is not like a fully CSS-aware browser). This in particular is why whenever we include "controlled" images in PDF reports (e.g. resources in custom conformance certificates, test case documentation), you are always given the option to preview and tune the display if things don't render as expected. Finally, keep in mind that this is test data that is potentially invalid, meaning that something that should be an image may actually be something else (which the test session could detect but would not be directly known to the PDF report generation).

In brief, including arbitrary images in PDF reports is quite a pain, and even if attempted, has so many quirks that you could easily end up with missing images and broken reports. As such, I think we'll have to reject this request (at least until something changes that makes it safer). I hope this is not a blocking point for you?

[olw-medcom]

That's quite alright, maybe there is another solution? You see the problem we are trying to solve is that we would like to upload the execution of a test suite to our external SVN (file repository) and we would like a single button that downloads the entire test execution that we can drop into our SVN. Do you think it would be possible to somehow download a zip file containing the report, which then references files? So instead of [File content] it will state [File content A], [File content B], [File content C], etc. and then these are in the zip file?

[costas80]

Hmm there is a way currently to achieve this although its not 100% straightforward.

The itb-ui container includes a volume mounted at path /gitb-repository. Under this you find the folder:

/status-updates/YEAR/MONTH/DAY/TEST_SESSION_ID

As an example, this is from my local env for a test session launched today (January 15th 2026):

/gitb-repository/status-updates/2026/1/15/98fa7d18-a06f-4038-a16f-7d9a8a2552b4

This includes all "raw" test step reports (XML files), the overall test report (if already generated), the log file, and in a data subfolder, all file content (including the images you are looking for). I'm skeptical about providing a feature on the UI to download all this as a bundle, given that this could end up being quite large. However, you could achieve the same (and better I believe) as follows:

1. In the community in question create a trigger that runs on test session completion. As input to this trigger ensure that you pass the test session identifier.
2. In the trigger's implementation (this could be an extra processing service endpoint in your supporting services app) you receive the test session identifier and use it to read the contents of the folder. You can then automatically take all such data and copy it to another location/repo (you do anything you want in the service).
3. To allow the trigger service to have access to the files, ensure it is part of the same overall service as the other ITB containers, and just mount (readonly) the same volume (the one mapped to /gitb-repository).

Besides making what you need available without any new features and UI updates, you will also 100% automate the process. Cool no?

Finally, note a couple points about this:

• On the first of every month the test session folders are zipped to "month archives" to save space. You shouldn't care about this however as upon test completion all files will be available.
• We don't guarantee stability in terms of the structure and contents of the /gitb-repository folder. However, I don't see any reason why this would change so you could in practice rely on its current structure.

[olw-medcom]

Interesting, I will have to look into this, thank you @costas80 !