Skip to content
Black November: every course and Teams plan at the lowest price of the year with code BLACKFRIDAY, through November 30. Shop the deal

Running Robot Framework Tests in CI with GitHub Actions

18-11-2026 Roy de Kleijn
Running Robot Framework Tests in CI with GitHub Actions

Tests are most useful when they run on their own, on every change, without anyone remembering to start them. GitHub Actions is a common way to do that, and Robot Framework fits it well.

The idea

A continuous integration pipeline checks out your code, installs what it needs, runs the tests, and keeps the results. If a test fails, the pull request goes red and the team knows before the change is merged. That fast feedback is the point.

A minimal workflow

A workflow is a YAML file in .github/workflows/. The core steps, using uv to manage the environment, look like this:

steps:
  - uses: actions/checkout@v4
  - uses: astral-sh/setup-uv@v5
  - run: uv sync
  - run: uv run robot tests/
  - uses: actions/upload-artifact@v4
    if: always()
    with:
      name: robot-results
      path: log.html

uv sync installs the project, uv run robot tests/ runs the suite, and the last step keeps the log even when the run fails, so you can open it and see exactly what happened. That if: always() matters: you want the log most when the tests are red.

Making it work in practice

Two habits make CI runs pleasant rather than painful. Use tags so a pull request can run a quick smoke set while the full suite runs nightly. And lean on the log and report that Robot Framework produces, since they turn a red build into a quick diagnosis rather than a guessing game.

Setting this up well, including headless browsers, parallel runs and combined reports, is part of running Robot Framework like a professional. Our Robot Framework Certified Professional course covers reliable execution and reporting as part of the full picture, and prepares you for the RFCP exam.

Frequently asked questions

Can Robot Framework run in GitHub Actions? Yes. A short workflow checks out the code, installs with uv, runs uv run robot, and uploads the log and report as artifacts.

How do I keep the report from a failed run? Upload it as an artifact with if: always(), so the step runs whether the tests passed or failed.

Can I run only a subset in CI? Yes. Tag your tests and use --include so a pull request runs a fast smoke set, with the full suite on a schedule.


Next: understanding logs and reports, or tags in Robot Framework.

Share:
Roy de Kleijn

Test Automation Expert

With over 15 years of experience in software testing and test automation, Roy helps teams improve their testing processes.

Get Robot Framework certified

Go from the basics to exam-ready at your own pace with the online RFCP course.