Artifact Support (Screenshots, Videos, Logs) in Currents Generic Reporter Context

Our CI pipeline runs end-to-end tests (Detox + Jest) for a React Native application. Due to current limitations with the @currents/jest reporter in a CommonJS environment, we’re using a workaround that converts JUnit XML reports into Currents reports for upload.

This flow works functionally but lacks one key capability: attaching artifacts (screenshots, videos, logs) to the test results. These files are essential for debugging failures and verifying UI regressions in mobile E2E testing.

Problem
Currently:

• The JUnit → Currents conversion format doesn’t support artifacts.

• The Jest reporter also doesn’t include any mechanism for uploading files, as it uses the same generic Currents upload command.

• As confirmed by Currents support (Miguel, 22 Oct 2025), “right now it is not supported,” and this applies to both JUnit and Jest reporters.

This limitation means that for frameworks like Detox or Cypress, where screenshot and video evidence are a standard part of test artifacts, Currents reports lose critical debugging data.

Proposed Solution
Add artifact attachment support to the generic Currents reporter and the data format reference, allowing uploads of associated files such as:

• Test-level screenshots and videos (e.g., recorded per test case)

• Test-level Log files or trace dumps

• Possibly, arbitrary attachments (e.g., JSON results or CLI outputs)

Ideally, this would work both:

• When uploading via the CLI (currents upload ...), referencing artifact file paths in metadata.

• And when using reporter integrations (@currents/jest), automatically attaching files from known locations (like artifactsDir) based on testName or other matching identification.

Impact
Adding artifact support would:

• Greatly improve debugging and analysis of E2E test failures.

• Bring Currents in line with other reporting platforms (like Allure or TestRail integrations).

• Enable teams to migrate fully to Currents even when not using supported reporters directly (e.g., when working through converted reports).

• Reduce friction for users in monorepos, CI pipelines, or multi-environment setups where direct ESM usage isn’t feasible.

Additional Notes

• Miguel mentioned the team “has plans to bump the generic reporter to support more things,” but no ETA is available.