v2.1.0 - Add execution_method, deprecate crowd

Deprecations / Replacements

A new execution_method parameter replaces the now-deprecated crowd parameter. You may not use both parameters together. If neither parameter is set the run will use the Run Group's execution method.

What	Then	Now
Running tests using the Tester Community	crowd: default	execution_method: crowd
Running tests using the Automation Service	crowd: automation	execution_method: automation
Running automatable tests using the Automation Service and non-automatable tests using the Tester Community	crowd: automation_and_crowd	execution_method: automation_and_crowd
Running tests using your On-Prem testers	crowd: on_premise_crowd	execution_method: on_premise

v2.0.0 - Remove deprecated conflict options

🔴 Breaking changes

The deprecated abort and abort-all options for the conflict parameter are no longer supported. Use cancel or cancel-all instead. (#14)

v1.1.0 - Support new conflict parameter options

🛠️ Fixes

• Support the new cancel and cancel-all options for the conflict parameter

⚠️ Deprecations

• The abort and abort-all options for the conflict parameter are now deprecated. Use cancel or cancel-all instead.

v1.0.1 - Rerunning a workflow with no run

🐛 Fixes

Rainforest Run IDs are now only persisted for a single workflow run attempt. This means that when rerunning a workflow, if the Rainforest rerun creation fails, the next attempt will create a full run rather than attempting to create the failed rerun a second time. (#9)

v1.0.0 - Rerun failed tests

🆕 Features

Rerun failed tests only when rerunning a failed workflow. With the initial releases of this gem, rerunning a failed workflow meant rerunning the full test suite. As of this release, only the failed tests will be rerun. This is particularly useful when a test failed because it needed to be updated (for example, to fix an out-of-date screenshot), or because there was a blip with your testing environment.

v0.0.2 - Custom URL support

🆕 Features

This release adds a new custom_url parameter, which maps to the Rainforest CLI's --custom-url flag. Note that if you use this parameter together with the environment_id parameter, the latter will be ignored.

🛠️ Fixes

No more No files were found with the provided path: results/rainforest/junit.xml. No artifacts will be uploaded. warnings logged when a run isn't created.

🧹 Housekeeping

We now have a test suite for this Action!

v0.0.1 - Initial Release

🆕 Features

First release, so everything is new ✨ Easily run tests in a run group from your GitHub workflows using the new Rainforest GitHub Action. See our base example for how to do so:

Base usage
This is a simple workflow file that will start a Rainforest run using run group #1234 every time a commit is pushed to the main branch. To use it, change the run group ID to the one you wish to run, ensure your Rainforest API token is properly configured in your GitHub secrets, and commit this file in your repo at .github/workflows/rainforest.yml.

on:
  push:
    branches:
      - main
jobs:
  rainforest:
    runs-on: ubuntu-latest
    name: Run Rainforest
    steps:
      - name: Rainforest
        uses: rainforestapp/rainforest-github-action@master
        with:
          token: ${{ secrets.RAINFOREST_API_TOKEN }}
          run_group_id: 1234