Skip to content

E2E:CI reporting Xray

Jump to bottom
Victor Alber edited this page May 20, 2026 · 1 revision

E2E CI, reporting & Xray

This page centralizes shared reporting and CI concepts for Ledger Live E2E tests. Platform-specific workflow inputs and commands live in Desktop E2E and Mobile E2E.

Allure

All test results are collected and reported through Allure. The Allure dashboard provides detailed reports for each test case, including executed steps, screenshots, logs, failures, and execution trends over time.

Allure makes it easier to track test performance and identify issues quickly.

Accessing CI Reports

After a workflow run, you need to be connected to the green VPN to access the Allure report. If the report does not open:

  • Make sure you are connected to the green VPN.
  • Try opening the report in an incognito window to avoid cache or session issues.

Local Reports

Local Allure generation depends on the platform:

Slack

E2E test results are integrated with Slack for real-time notifications. Results are posted in the #live-repo-health channel and include:

  • A direct link to the Allure report.
  • A link to the CI run where the tests executed.

This keeps the channel informed about failures and scheduled run status.

Xray

To send test results to Xray, enable the workflow input that exports test results and provide the corresponding Jira Test Execution key.

Desktop uses a single Test Execution input. Mobile exposes separate Android and iOS execution keys:

  • test_execution_android
  • test_execution_ios

See the platform pages for the current workflow input tables.

CI Runs

E2E tests can be run manually from GitHub Actions and also run on schedules. Use manual runs when you need targeted validation for a branch, specific test files, or a platform-specific workflow configuration.

Desktop Speculos tests can be triggered with the @Desktop - UI e2e - Test App workflow.

Mobile E2E tests are triggered through the [Mobile] E2E Only - Scheduled/Manual workflow and the reusable workflow documented in Mobile E2E.

Sharding

CI uses sharding to reduce execution time by splitting test suites into smaller groups that run in parallel.

  • Mobile uses the generate-shards-matrix action to calculate shard counts dynamically for manual, release, and scheduled runs.

Keep the platform-specific sharding details on the platform pages because the implementation differs.

Broadcast

Transaction broadcasting is intentionally controlled in CI. See Speculos transaction broadcast policy.

Investigating Failures

Start with the same high-level checks for both platforms:

  1. Check screenshots in the Allure report. They are captured at the point of failure and often show the first visible symptom.
  2. Review logs generated during test execution.
  3. Rerun the failed test in isolation if needed to reproduce and analyze it.
  4. Use platform-specific debugging guidance:

Clone this wiki locally