RSpec Integration with CI Insights
Report your test results from RSpec to CI Insights
This guide explains how to integrate RSpec with CI Insights using the
rspec-mergify gem. Once installed, test results are automatically uploaded to
CI Insights without any extra workflow changes.
Installation
Section titled InstallationYou need to install the
rspec-mergify gem to automatically
upload your test results to CI Insights.
Gemfile
Section titled GemfileAdd the gem to your Gemfile:
group :test do gem 'rspec-mergify'endThen run:
bundle installGem Install
Section titled Gem InstallAlternatively, install it directly:
gem install rspec-mergifyUpdate Your CI Workflow
Section titled Update Your CI WorkflowYour workflow should run your tests as usual while exporting the secret
MERGIFY_TOKEN as an environment variable.
GitHub Actions
Section titled GitHub ActionsAdd the following to the GitHub Actions step running your tests:
env: MERGIFY_TOKEN: ${{ secrets.MERGIFY_TOKEN }}For example:
- name: Run RSpec Tests 🧪 env: MERGIFY_TOKEN: ${{ secrets.MERGIFY_TOKEN }} run: bundle exec rspecBuildkite
Section titled BuildkiteSet MERGIFY_TOKEN as an environment variable in your pipeline step:
steps: - label: "Run RSpec Tests 🧪" command: bundle exec rspec env: MERGIFY_TOKEN: "${MERGIFY_TOKEN}"The gem automatically collects your test results and sends them to CI Insights.
Check the CI Insights dashboard afterward to view execution metrics, detect flaky tests, and review test trends.
Environment Variables
Section titled Environment Variables| Variable | Purpose | Default |
|---|---|---|
MERGIFY_TOKEN | API authentication token | Required |
MERGIFY_API_URL | API endpoint location | https://api.mergify.com |
RSPEC_MERGIFY_ENABLE | Force-enable outside CI | false |
RSPEC_MERGIFY_DEBUG | Print spans to console | false |
MERGIFY_TRACEPARENT | W3C distributed trace context | Optional |
MERGIFY_TEST_JOB_NAME | Test job name identifier | Optional |
Was this page helpful?
Thanks for your feedback!