Ensuring `record tests` always runs

Search…

This page relates to Recording test results.
The launchable record tests command must be executed after you run tests.
However, some tools exit the build process as soon as the test process finishes, preventing this from happening.
The way to fix this depends on your CI tool:
Jenkins
Jenkins has post { always { ... } } option:
pipeline {
  ...
  sh 'bundle exec rails test -v $(cat launchable-subset.txt)'
  ...
  post {
    always {
      sh 'launchable record tests <BUILD NAME> [OPTIONS]'
    }
  }
}
CircleCI
CircleCI has when: always option:
- jobs:
  - test:
    ...
    - run:
        name: Run tests
        command: bundle exec rails test -v $(cat launchable-subset.txt)
    - run:
        name: Record test results
        command: launchable record tests <BUILD NAME> [OPTIONS]
        when: always
Github Actions
GitHub Action has if: ${{ always() }} option:
jobs:
  test:
    steps:
      ...
      - name: Run tests
        run: bundle exec rails test -v $(cat launchable-subset.txt)
      - name: Record test result
        run: launchable record tests <BUILD NAME> [OPTIONS]
        if: always()
Bash
If you run tests on your local or other CI, you can use trap:
function record() {
  launchable record tests <BUILD NAME> [OPTIONS]
}
# set a trap to send test results to Launchable for this build either tests succeed/fail
trap record EXIT SIGHUP
​
bundle exec rails tes

Converting test reports to JUnit format

Managing complex test session layouts

Last modified 1mo ago

Copy link

On this page

Jenkins

CircleCI

Github Actions

Bash