ceven

Saucelabs

Triggers automated test suites across browsers and devices, monitors job failures in real time, and alerts engineering teams when regressions hit production.

Try Saucelabs in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Saucelabs integration

    • Describe the outcome and Ceven picks the right Saucelabs calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Saucelabs data, across all 6 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Saucelabs access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Saucelabs, when, and on whose behalf.
    • The agent pauses and asks when Saucelabs is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Saucelabs.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Saucelabs action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Saucelabs, and when to use it.

Get Performance API Definition
Use this when you need to retrieve the OpenAPI documentation to understand schemas for the Performance API.
Get API Status
Pull the current operational status of Sauce Labs services to check for outages or wait times.
Get Appium EOL
Retrieve end of life timestamps for Appium versions to plan version upgrades.
Get Supported Platforms
Pull the list of available platforms for Appium or WebDriver to verify device availability.
Get Tunnel Versions
List available Sauce Connect tunnel versions to ensure the local proxy is up to date.
List Jobs
Pull all test execution jobs for a user with filters for time range or job type.
List VDC Jobs
Retrieve virtual device cloud testing history and specific job details for mobile runs.
Check Platform Support
Use this to confirm if a specific browser version is currently supported on the grid.
Monitor Tunnel Health
Check if the Sauce Connect tunnel is active and running the latest binary.
Fetch Job Logs
Pull the logs for a specific job ID to analyze why a test failed.
Verify API Availability
Run a status check on the Sauce Labs API before starting a large test batch.
Audit Appium Versions
Compare current project Appium versions against the end of life list.

12 actions · scroll to see them all

Frequently asked questions

Ceven connects to Sauce Labs using your username and access key. We store these credentials in an encrypted vault that is isolated from the model. When an agent needs to perform an action, it retrieves the key to sign the API request and then discards it from memory. You can rotate your Sauce Labs access key at any time in your account settings, and simply updating the key in the Ceven integration panel restores connectivity. We never share these credentials with third party tools or store them in plain text logs.
Ceven can trigger a new test run if it detects a failure, but it does so by calling your CI CD pipeline rather than interacting with the Sauce Labs grid directly. Because Sauce Labs is a destination for test execution and not the test author, Ceven tells your build server to re run the specific job. This ensures that the entire setup process, including environment variables and app uploads, happens correctly. The agent then monitors the new job ID to see if the failure was flaky or a persistent regression.
Yes. Ceven can query and monitor jobs across the entire Sauce Labs ecosystem, including the Virtual Device Cloud and real device clouds. When you ask the agent to list jobs or check platform support, it pulls data from both sources. You can specify in your workflow if you only want to be alerted about failures on real devices, which is useful for catching hardware specific bugs that do not appear in emulated environments during the early stages of a sprint.
Sauce Labs imposes rate limits on their API endpoints to ensure platform stability. If Ceven hits a 429 Too Many Requests response, the agent automatically implements an exponential backoff strategy. This means it will wait a few seconds before retrying the request. For very large organizations with thousands of concurrent jobs, we recommend scheduling summary reports every hour rather than requesting a full job list every minute to avoid hitting these limits and causing temporary gaps in your monitoring dashboards.
Yes. Ceven can use the tunnel versions tool to check if your current tunnel binary is outdated. If you set up a monitoring workflow, the agent can notify your DevOps team the moment a new version is released or if the current tunnel status indicates a disconnection. While Ceven cannot physically install the software on your local server, it provides the exact download link and version number needed to resolve the issue, reducing the time spent on infrastructure debugging.
The agent regularly polls the Appium EOL endpoint to maintain a local map of version expiration dates. You can create a workflow that compares the versions listed in your test configuration files against this list. When a version is within thirty days of its end of life, Ceven can automatically create a ticket in your backlog. This prevents the common scenario where tests suddenly stop running because the cloud provider discontinued support for an old driver version without the team noticing.
Ceven can pull the Performance API definitions and the resulting data from your runs to summarize trends. While Sauce Labs provides its own dashboards, Ceven allows you to pull that data into a larger context, such as comparing performance metrics against a recent code change in GitHub. The agent can read the JSON output of a performance test and highlight regressions in page load times or API response durations, sending a summary to your team before the build is promoted to staging.
Sauce Labs paginates its job lists. Ceven handles this pagination automatically by walking the cursors until it finds the data you requested. However, requesting a list of every job ever run for a high volume account can be slow and may time out. We recommend using filters like time range or job status in your prompts. By asking for failed jobs from the last twenty four hours instead of all jobs, the agent can return results in seconds rather than minutes.

Alternatives to Saucelabs

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

BrowserStack logoBrowserStackLambdaTest logoLambdaTestPerfecto logoPerfecto

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Saucelabs and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free