← redevops.ioEdge Sentinel →
Pre-release · developer tool

One QA runtime. Multiple test engines.

Keep your existing browser, mobile and keyword-driven automation. ReDevOps QA aims to standardize orchestration, execution evidence and verification across engines without requiring a framework rewrite.

Status: pre-release, public repository, first release published. The code is at github.com/redevops-io/redevops-qa. Since November 2026 it ships as a public, signed container image — ghcr.io/redevops-io/redevops-qa:0.6.3 (tag v0.6.3) — for Docker Compose or Kubernetes; there is still no package on PyPI, so a source install builds from a checkout. It is built against pinned releases of runtime-contracts (v0.3.15 and v0.3.16) and agent-harness (v0.2.0), recorded with their digests in pins.toml. It is source-available, not open source: AGPL-3.0-or-later as modified by the Commons Clause, the family licence. This page says what has been tested and how, and what has not. It is also one of three products in the combined install with Projects, Sidekick and Edge Sentinel.
View the repository → Combined install → Join the pilot →

The problem

Teams rarely have one test framework. Browser checks run in Playwright or Selenium, keyword suites in Robot Framework, mobile checks in Appium. Each engine has its own setup, its own artifacts and its own idea of what a pass means, so a release decision ends up stitched together by hand.

What the runtime does

ReDevOps QA is the layer around the engines, not another engine. It does not replace Playwright, Selenium, Robot Framework or Appium, and one engine does not run another engine's tests unchanged. A project can use more than one engine and read all of the results through one contract.

request and policy → QA runtime → engine adapter → supervised worker → evidence bundle → independent verifier
Optional agent and context layers sit above the request. The runtime pins releases of runtime-contracts and agent-harness; a shared runtime does not mean a shared process.

Engines and what has been shown

Playwright

Real browser in CI

Interactive browser adapter on real Chromium. The CI lane passed 28 tests on Ubuntu 24.04 with Playwright 1.64.1.

Selenium

Real browser in CI

Interactive adapter and a pytest suite adapter. The CI lane runs real Chrome 156 with Selenium 4.52.0 and passed 11 tests.

Robot Framework

Real framework in CI

Suite adapter with a library allow-list and strict report import. The CI lane runs Robot Framework 7.5 and passed 10 tests. No browser is involved.

Appium (Android)

Experimental

The CI lane starts a real Appium server with no device. A device-backed session was observed to pass locally on an emulator, never in CI.

Appium (iOS)

Not available

The adapter reports UNAVAILABLE. iOS needs a macOS and Xcode host that you supply; no evidence exists yet.

Evidence behind each level

EngineLevelWhat was runWhere and when
PlaywrightReal engine, CI28 tests, 0 skipped, 0 failed; Playwright 1.64.1, Chromium installed by PlaywrightGitHub Actions, ubuntu-24.04; commit 938eb48, 1 November 2026 (UTC); run 41261799543, job 124716422274
SeleniumReal engine, CI11 tests, 0 skipped, 0 failed; Selenium 4.52.0, Google Chrome 156.0.8078.47GitHub Actions; commit 938eb48, 1 November 2026 (UTC); run 41261799543, job 124716398989
Robot FrameworkReal engine, CI10 tests, 0 skipped, 0 failed; Robot Framework 7.5GitHub Actions; commit 938eb48, 1 November 2026 (UTC); run 41261799543, job 124716399117
Appium, serverReal server, no device, CIAppium 3.9.0 server, UiAutomator2 driver 8.7.3, Python client 6.1.1; shows the client and driver accept the adapter's capabilities and that a worker without a device is UNAVAILABLE; drives no appGitHub Actions; commit 938eb48, 1 November 2026 (UTC); run 41261799543, job 124716399113
Appium, Android deviceObserved once, local onlyOne test (the Settings app opens and the screenshot is a real PNG), three runs in a row, against an Android 17 (API 37, arm64) emulator on an Apple-silicon MacLocal, 1 November 2026, recorded in the repository's Appium README. Not run in CI: hosted runners have no emulator. Other API levels, x86_64, physical devices and iOS are not verified
Appium, iOSNoneThe adapter reports UNAVAILABLENo run

The real-engine lanes for Selenium, Robot Framework and the Appium server are not yet required checks on the repository's main branch. The offline adapter tests (fake browsers and devices, recorded real reports) run on every change. Dependency pins are runtime-contracts v0.3.15 and v0.3.16 and agent-harness v0.2.0.

What this does not claim

Prerequisites and limits

Get it, licence and access

The repository is public and pre-release. There are two ways to run it today; there is still nothing on PyPI.

1. The signed image (recommended). ghcr.io/redevops-io/redevops-qa:0.6.3, index digest sha256:54d8064caef7e9798bff2009c841103a37451ecd4e7fc9f1cbf44c9bf8dff779 (linux/amd64 + linux/arm64): public, signed keyless with cosign by the workflow that built it, with a GitHub build-provenance attestation and a BuildKit SBOM. It runs as uid 10001, refuses to start without credentials and publishes on loopback by default; the image adds a small authenticated HTTP service that serves the static HTML report and a browser UI at /ui/. The image lanes run on Linux x86_64; the arm64 image can verify and report on evidence but cannot run the lanes. Verify before the first pull, then follow the standalone install guide:

cosign verify ghcr.io/redevops-io/redevops-qa@sha256:54d8064caef7e9798bff2009c841103a37451ecd4e7fc9f1cbf44c9bf8dff779 --certificate-identity 'https://github.com/redevops-io/redevops-qa/.github/workflows/oci-release.yml@refs/heads/main' --certificate-oidc-issuer https://token.actions.githubusercontent.com

2. A checkout. The checkout is a pre-release state, and its dependencies are pinned in pins.toml. Engines, browsers and drivers are installed separately.

git clone https://github.com/redevops-io/redevops-qa

The install configurator turns a choice of engines and host into the exact pinned steps. It runs in your browser, runs nothing for you and marks what is verified, experimental or not offered.

ReDevOps QA is source-available, not open source: the family licence, AGPL-3.0-or-later as modified by the Commons Clause, the same terms as the other rAIls packages. The repository states that the public licence of the finished product is not final. Vulnerability reporting is described in the repository's SECURITY.md. To try it on your own suite with us, join the pilot.

Part of the combined install

redevops-qa is one of three products in a single documented install, alongside Projects and Sidekick (the operator console and chat) and Edge Sentinel, on one Docker host. Projects registers exactly what a product-registry file lists — no code flags, no per-product forks — and the three products share one approval secret, so an approval clicked in Projects is verified by every product that has to act on it. A real recorded install and walkthrough, both install paths (a single-pull signed bundle or a from-source checkout), and the digests to verify are on the combined install page.

The stated limitations (QA's browser lanes are linux/amd64 only, so they run under Rosetta/QEMU on Apple Silicon hosts — slower, not native-ARM64 evidence) and the release gate that re-runs the file-secrets path on every change: deploy/combined/README.md. Edge Sentinel's own product page and standalone install are at redevops.io/sentinel.

View the repository → Combined install + demo → Join the pilot → Why we built it, and what rAIls adds →

// ReDevOps QA · pre-release · evidence as of commit 938eb48 (1 November 2026, UTC) · Playwright, Selenium, Robot Framework and Appium are trademarks of their respective owners and are used here to name the engines the adapters drive; this is an independent project, not endorsed by them.