Skip to main content

Install TestVibe

Choose the package for your infrastructure. Use the versions and download links on the portal.

What is included​

  • The application includes Settings → Administration. PostgreSQL, migrations, object storage, test execution and browser services complete the stack.
  • The appliance includes a local recovery console. Compose and Kubernetes include the same recovery executable in the web image.

Prepare the host​

  • Use an x86-64 host for the complete stack. Start with at least 4 CPU cores and 8 GB RAM for evaluation, then size browser capacity against your workload.
  • Provide persistent database and artifact storage, DNS, and a browser-reachable application address. Use HTTPS when exposing the installation to your team.
  • Allow access to your application under test, configured identity/email/AI providers, and the customer registry when pulling containers. An external AI provider requires its own network access.

Download and verify​

  • Sign in to the on-prem portal with your subscription account. Choose Docker / Kubernetes, Hyper-V, or VMware / VirtualBox. Only published formats are offered.
  • Download the matching checksums and verify the files before importing or extracting them. Container and appliance versions may differ; check the version on each download card.

Hyper-V​

  • Extract the VHDX archive and decompress both .vhdx.zst files with zstd.
  • Create a Generation 2 VM. Use the Microsoft UEFI Certificate Authority Secure Boot template for Linux, or disable Secure Boot if your host cannot use that template.
  • Attach both the OS disk and data disk, connect the network adapter, and boot. Open the application address shown on the console.
  • For an upgrade, preserve your existing data disk and attach only one disk labeled testvibe-data.

VMware and VirtualBox​

  • Import the OVA; it includes both disks. Connect the network adapter and allocate CPU and memory for your workload.
  • For VirtualBox, enable EFI before the first boot.
  • Boot, wait for initialization, then open the application address shown on the console.

Docker Compose​

  • Download and extract the current bundle. Copy .env.example to .env and set the required database, blob signing, blob admin and runner secrets. Keep an existing secret-protection key unchanged.
  • Authenticate with docker login testvibe.azurecr.io using your subscription registry credentials.
  • Run docker compose up -d. Open http://localhost:3000, choose Create an account, and finish setup in Settings → Administration.
  • For remote access, configure public application and artifact URLs in .env (ports 3000 and 8080 by default) and restart the affected services. Do not use container DNS names as public URLs.
cp .env.example .env
# Generate a different value for each required secret:
openssl rand -hex 32
# Set TV_PG_PASSWORD, TV_BLOBSERVER_SIGNING_KEY,
# TV_BLOBSERVER_ADMIN_KEY and TV_RUNNER_KEY in .env.
# For team access, set TESTVIBE_PUBLIC_BASE_URL to the app address
# and TV_BLOBSERVER_PUBLIC_URL to the artifact address.
docker login testvibe.azurecr.io
docker compose up -d

Kubernetes​

  • Create the testvibe namespace, then a registry pull secret for testvibe.azurecr.io and configure global.imagePullSecrets. Authenticate Helm to the same registry.
  • Install the chart from oci://testvibe.azurecr.io/charts/testvibe at the version shown on the portal, or use the chart in the bundle.
  • Supply secrets.pgPassword, secrets.blobSigningKey, secrets.blobAdminKey and secrets.runnerKey. Keep any existing secrets.protectionKey unchanged. Use a values file or your secret manager.
  • Configure ingress and persistent volumes for your cluster. Wait for migrations and web readiness, then open the application and create the first administrator. No admin deployment or admin password is required.
helm registry login testvibe.azurecr.io
helm install testvibe oci://testvibe.azurecr.io/charts/testvibe \
  --version <version> --namespace testvibe --create-namespace \
  --values installation-values.yaml

Use the version from your chosen portal release. For a complete protected values file and registry setup, see Install on Kubernetes. See Install the appliance for disk import and VirtualBox commands.

Create the first user​

Follow first boot and setup. New installations use normal signup; existing installations retain their users and use host recovery to appoint an instance administrator.