Skip to main content

Overview

Stably Cloud provides scalable infrastructure for running your Playwright tests with high parallelism, AI-powered features, and comprehensive reporting. Your tests run in the cloud while using your existing playwright.config.ts configuration.

Prerequisites

1

Publish Your Tests

Before running tests in the cloud, ensure your latest tests are published from the UI.
2

Get API Key

Obtain your API key from the settings page for API and CI integrations.

Running Tests in the Cloud

You can trigger cloud execution using several methods:

Using the Stably Web Editor

The easiest way to run tests in the cloud is directly from the Stably dashboard:
  1. Navigate to your project in the Stably dashboard
  2. Select the tests you want to run
  3. Click the Run button
  4. Choose your run configuration (projects, grep patterns, environment)
  5. Monitor results in real-time from the dashboard

Web Editor Guide

Learn more about the Stably Web Editor

Cloud Execution Features

High Parallelism

Run up to 100 workers in parallel for faster test execution. Contact us if you need more.

AI Auto-Heal

Tests automatically adapt to minor UI changes, reducing maintenance burden.

Smart Reporting

Get detailed insights with screenshots, traces, and AI-powered failure analysis.

Environment Management

Easily switch between environments and manage test data variables.

Monitoring Test Runs

After triggering a test run, you can monitor progress:
1

View Real-Time Progress

Navigate to your Stably dashboard to see:
  • Real-time test execution status
  • Pass/fail rates
  • Test duration and performance metrics
2

Review Results

Once tests complete, access:
  • Detailed test reports with screenshots
  • Trace files for debugging failures
  • AI-generated failure analysis
  • Historical trends and analytics
3

Receive Notifications

Get alerts via:
  • Email notifications
  • Slack messages
  • GitHub PR comments
Configure notifications in your project settings.

Best Practices

Organize tests into logical projects (smoke, regression, critical) for flexible execution strategies.
Take advantage of cloud workers by ensuring your tests are independent and can run in parallel.
Set appropriate retry counts for different test types. Critical tests might need fewer retries, while flaky tests might need more.
Track your test execution time and optimize slow tests to reduce costs and improve feedback time.

Troubleshooting

Problem: Getting 401 or 403 errors when using the APISolution: Verify your API key is correct and has proper permissions. Get a new key from the settings page.
Problem: Error saying specified project doesn’t existSolution: Ensure the project name matches exactly what’s defined in your playwright.config.ts
Problem: Tests are taking longer than expectedSolution:
  • Increase worker count for better parallelism
  • Check if tests have dependencies preventing parallel execution
  • Review individual test timeouts

Next Steps