Artifacts
Download artifacts or reports for a completed test run by upload ID. Use this command when you need to retrieve artifacts from a run that was submitted with --async, or to download reports independently after the fact.
dcd artifacts --upload-id <id> [flags]Flags
Authentication
--api-key <key>
Your DeviceCloud API key. Defaults to DEVICE_CLOUD_API_KEY env var
Required
--upload-id <uuid>
UUID of the completed upload to download artifacts for
Artifact Download
--download-artifacts <ALL|FAILED>
Download a zip of logs, screenshots, and videos. ALL includes every test; FAILED includes only failed tests. Mutually exclusive with --report
--artifacts-path <path>
Output path for the artifacts zip (default: ./artifacts.zip). Requires --download-artifacts
Report Download
--report <format>
Download a test report. Options: junit, html, html-detailed, allure. Mutually exclusive with --download-artifacts
--allure-path <path>
Output path for the Allure report (default: ./report.html). Requires --report allure
--html-path <path>
Output path for the HTML report (default: ./report.html). Requires --report html or html-detailed. The HTML report downloads as a ZIP, so use a .zip path such as ./report.zip
--junit-path <path>
Output path for the JUnit report (default: ./report.xml). Requires --report junit
Other
--debug
Enable detailed debug logging
Examples
Download artifacts for all tests:
Download artifacts for failed tests only, to a custom path:
Download a JUnit report:
Download an Allure report to a custom path:
Using with Async Runs
dcd artifacts is especially useful alongside --async. Submit the run without blocking, then retrieve artifacts later:
See Async Execution and Report Formats for more details.
Last updated