# Add support for adding log & other files for Test Reports add-on

**URL:** <https://discuss.bitrise.io/t/add-support-for-adding-log-other-files-for-test-reports-add-on/9494>\
**Category:** Released\
**Created:** [July 3, 2019, 12:20pm UTC](https://discuss.bitrise.io/t/add-support-for-adding-log-other-files-for-test-reports-add-on/9494 "2019-07-03T12:20:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![piotr.zawadzki](https://avatars.discourse-cdn.com/v4/letter/p/d78d45/32.png) [@piotr.zawadzki](https://discuss.bitrise.io/u/piotr.zawadzki)\
**Post date:** [July 3, 2019, 12:20pm UTC](https://discuss.bitrise.io/t/add-support-for-adding-log-other-files-for-test-reports-add-on/9494/1 "2019-07-03T12:20:34Z")

</div>

## Description of the feature request

I would like to request for an option to upload log & compressed files as well. According to the doc this should be possible now:

> **[Exporting to test results from any Step](https://docs.bitrise.io/en/bitrise-ci/testing/exporting-to-test-reports-from-any-step.html)**
>
> You can export test results from any Step using the Export test results to the Test reports Step. Alternatively, you could configure your own Script Step to export the files.

> The Step then moves every artifact that is deemed a test result into the Step’s test result directory: test result files, test attachments, logs, screenshots, and so on.

Currently, only image files are uploaded to test reports add-on.

## Use case / for what or how I would use it

We have a workflow in which we run Android instrumentation tests on an emulator. Apart from JUnit test results we also get screenshots of failing tests, log files from ADB logcat and a compressed folder with JUnit HTML reports. It would be nice to access them from the test reports as stated on [Exporting to test results from any Step](https://devcenter.bitrise.io/testing/exporting-to-test-reports-from-custom-script-steps/)

I’ve described the changes needed in the Deploy step:

> <https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues/92>
>
> Hi,
> First of all thanks for introducing the Test Reporting add-on - we use it i…n our project and it makes much easier to see what went wrong in a build.
> 
> I would like to request one additional feature i.e. an option to upload log & compressed files as well. According to the doc this should be possible now:
> https://devcenter.bitrise.io/testing/exporting-to-test-reports-from-custom-script-steps/
> 
> \>The Step then moves every artifact that is deemed a test result into the Step’s test result directory: test result files, test attachments, logs, screenshots, and so on.
> 
> I've noticed that only image files are copied though.
> I've forked the library & enabled additional file types: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/compare/master...stepstone-tech:additional-test-artefact-support?expand=1
> 
> Obviously, method names should be changed etc. if this is to be merged into this repo.
> 
> Can you add official support for non-image artifacts as well please?

---

<div class="post-metadata">

**Author:** ![bitce](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/bitce/32/1639_2.png) [@bitce](https://discuss.bitrise.io/u/bitce)\
**Post date:** [July 4, 2019, 12:43pm UTC](https://discuss.bitrise.io/t/add-support-for-adding-log-other-files-for-test-reports-add-on/9494/2 "2019-07-04T12:43:54Z")

</div>

Thanks for the #feature-request here as well @piotr.zawadzki! Please make sure to vote for it!

---

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [July 4, 2019, 3:50pm UTC](https://discuss.bitrise.io/t/add-support-for-adding-log-other-files-for-test-reports-add-on/9494/3 "2019-07-04T15:50:45Z")

</div>

Hi @piotr.zawadzki, thanks for the #feature-request!

Just wanted to mention as a workaround that you can attach those additional artifacts to the build ( [https://devcenter.bitrise.io/tips-and-tricks/attach-any-file-to-build/](https://devcenter.bitrise.io/tips-and-tricks/attach-any-file-to-build/) ). With that you’ll be able to access them from the Build’s page.

---

<div class="post-metadata">

**Author:** ![piotr.zawadzki](https://avatars.discourse-cdn.com/v4/letter/p/d78d45/32.png) [@piotr.zawadzki](https://discuss.bitrise.io/u/piotr.zawadzki)\
**Post date:** [July 4, 2019, 7:01pm UTC](https://discuss.bitrise.io/t/add-support-for-adding-log-other-files-for-test-reports-add-on/9494/4 "2019-07-04T19:01:06Z")

</div>

Hi @viktorbenei,  
Thanks! That’s actually what we were doing before. I just find having them in the same place a bit easier and faster to use.

I found a different workaround as well. I simply add a non-forked Deploy to Bitrise step in addition to my custom version of it. It does deploy the artifacts twice but at least the artifacts are present on the test reports as well 🙂
