Execution Modes
- Blocking mode: Pipeline waits for test completion before proceeding
- Non-blocking mode: Tests run asynchronously, results sent via Slack/email notifications
Setup Instructions
1
Create API Key Secret
First, get your API key from the settings page on the Web UI.Then, go to your GitHub repository, click on “Settings” > “Secrets and variables” > “Actions”. Create a new Repository Secret named 
STABLY_API_KEY and paste your API key into the secret value.2
Get Test Suite ID
From a test suite’s page, click on the 
Add to CI button to get the code snippet that contains the test suite ID.3
Create Workflow File
Create the file 
.github/workflows/stably.yaml in your GitHub repository and paste the code snippet there.Basic Configuration
Pull Request Testing
For PR testing, you can use environment variables and other parameters to customize test execution:Advanced Configuration Options
The GitHub Action supports various options to customize test execution:- number-of-workers: Control parallel execution (1-10 workers)
- retries: Set retry attempts for failed tests
- repeats: Run each test multiple times for reliability testing
- operation-delay-ms: Add delays between test operations
- test-timeout-ms: Set individual test timeout limits
- notification-profile: Configure result notifications
- note: Add contextual information to test runs
- environment: Specify test environment (PRODUCTION, STAGING, DEVELOPMENT) for variable overrides
- variable-overrides: Override test variables with custom values (JSON format)
Adding Notes to Test Runs
When running multiple test suites concurrently, attach descriptive notes using thenote parameter:
- Distinguish between concurrent test runs
- Add contextual information to test executions
- Improve test result tracking and analysis