Many tests generate image files (screenshot tests, XCUITests, etc). At the time of writing (August 2025), Bitrise Test Reports automatically collates image files with associated test cases for Xcode tests (using the xcresult file). What if your test doesn't generate an xcresult file? This guide will show you how to achieve the same thing.
Example of image files shown in-line with the associated test case
Below is an example bitrise.yml snippet that demonstrates how a workflow will dynamically trigger or skip fanout.
parent: the top level workflow. Reads env vars to decide whether to fanout. When it does fanout, it also collects artifacts from child builds._test_shard: a reusable utility workflow that publishes a dummy artifacttest_shard_1 and test_shard_2: set an env var to customize behavior of _test_shard, which it triggers
To generate a slather report and publish it as an artifact, add a script step to your workflow. The contents of the step will look something like:
gem install slather
# for all options, see: https://github.com/SlatherOrg/slather
slather coverage --scheme $SCHEME_NAME $BITRISE_PROJECT_PATH --html --output-directory $BITRISE_DEPLOY_DIR/slather
| --- | |
| format_version: '11' | |
| default_step_lib_source: https://github.com/bitrise-io/bitrise-steplib.git | |
| project_type: other | |
| trigger_map: | |
| - push_branch: "*" | |
| workflow: fanout_parent | |
| workflows: | |
| fanout_child: | |
| steps: |