# Updated via Autotest Editor - 2026-05-27T09:41:49.880Z
# Source of truth: this YAML file
# Note: Expected results estimated based on step actions

id: pbx-availability-check-database_replication_and_sync_integrity
module: pbx
group: pbx-availability
title: Verify database replication between HA nodes maintains consistency and acceptable lag
description: Verify database replication between HA nodes maintains consistency and acceptable lag
priority: Medium
tags: []
references: []
dependencies:
  - label: Admin Portal
    value: https://pbx.local:4443 (configure via $BASE_URL)
  - label: Repository URL
    value: ${BASE_URL}/downloads or $REPO_URL
  - label: Protocol
    value: HTTPS + SIP (UDP/TCP/TLS) + RTP/SRTP
  - label: Load Gen
    value: SIPp or custom load generator + monitoring (Prometheus/Grafana recommended)
  - label: Credentials
    value: Admin user with sufficient privileges (portal + SSH where needed)
  - label: Test Data
    value: Clean test tenant or lab PBX instance (recommended isolated environment)
preconditions: []
postconditions: []
steps:
  - action: Open admin portal or repository URL in browser context
    expected: >-
      The admin portal or repository page loads successfully without errors, security warnings, or
      redirects.
  - action: Execute the main verification or configuration action described in the test
    expected: >-
      The primary action described in the test completes successfully and produces the expected
      state or output.
  - action: Capture evidence (screenshot, log, API response)
    expected: >-
      Relevant evidence (screenshot, log, or API response) is successfully captured and can be
      reviewed.
  - action: Assert expected outcome
    expected: >-
      All verification assertions pass and the system is confirmed to be in the expected final
      state.
automation_status: manual
file: tests/pbx/availability.spec.ts
custom_fields:
  original_action: check
  manualReason: Requires HA database cluster; verifying replication lag needs direct database access
automatable:
  - Most UI-driven configuration and verification steps via Playwright
notYet:
  - Requires HA database cluster; verifying replication lag needs direct database access
  - Requires external SIP endpoints or physical phones for media/audio validation
  - Hypervisor-level operations (vCenter, libvirt, vSphere) not reachable from browser automation
  - Long-running load or HA failover scenarios need dedicated lab infrastructure