Execution

Temporary test environments

QualityMax’s temporary-environment pilot uses E2B to host an application for a test run. It provisions a configured target, waits for its health check, runs a stored Playwright script, collects a result summary, and tears down the target. This adds an application environment lifecycle to test execution.

The pilot is restricted to QualityMax owners and staff and must be enabled and configured by an operator. It is not generally available to customer accounts.

In Temporary environments, choose a configured target and a stored Playwright test. Review the lifetime and estimated maximum target cost before launching. The run view shows the durable run status, recorded lifecycle phases, result summary, and whether teardown was confirmed. An unconfirmed teardown is not a successful cleanup; retain the run ID for operator investigation.

Targets come from a server-managed allowlist. This pilot does not accept an arbitrary repository, public demo URL, image, shell command, or credential from the page. Target admission enforces a configured monthly cost ceiling, and concurrent runs for the same target are rejected. Configuring access to the page does not enable the pilot or allocate a sandbox by itself.

Formbricks is the first intended commercial-product test target for this capability. Formbricks testing requires a configured self-hosted environment. This pilot description does not assert a completed Formbricks run or published evidence for its team.