Accelerate Release Confidence with FullShot Enterprise Edition

Deploying FullShot Enterprise Edition: Fast Visual Testing at Scale

Overview

FullShot Enterprise Edition is a self-hosted/managed solution for automated visual testing and screenshot capture across web applications. It centralizes capture, comparison, and collaboration so engineering and QA teams can detect UI regressions, verify releases, and maintain visual compliance at scale.

Key Capabilities

• Parallel screenshot capture: Run captures across many browsers and viewport sizes concurrently to speed coverage.
• Visual diffs & baselines: Automate pixel and perceptual comparisons against approved baselines with configurable thresholds.
• CI/CD integration: Plug into common pipelines (Git, CI providers) to run visual tests on commits, pull requests, and releases.
• Access controls & audit trails: Enterprise role management, SSO (SAML/OAuth), and immutable logs for compliance.
• On-premise or private cloud deployment: Keep screenshots and metadata inside corporate networks for data residency requirements.
• Collaboration features: Shared review workflows, inline comments, and issue linking for fast triage.

Deployment Architecture (typical)

• Capture workers: Autoscaled nodes (containers or VMs) that run headless browsers to take screenshots.
• API & web UI: Central server exposing REST APIs and a web app for reviewing diffs and managing projects.
• Storage layer: Object storage (S3-compatible or network storage) for images and a relational DB for metadata.
• CI runners / agents: Lightweight agents that trigger captures from pipelines or developer machines.
• Auth & networking: Integrate with corporate IdP, set up VPNs or private links, and configure ingress/egress rules.

Recommended Infrastructure (example for large teams)

• Kubernetes cluster with:
  • 2–3 control-plane nodes
  • Autoscaling worker pool for capture pods
  • Persistent volumes and S3-compatible object store
  • PostgreSQL (managed or HA deployment)
  • Redis for queuing and caching
• Load balancer, TLS termination, monitoring (Prometheus/Grafana), and centralized logging.

Deployment Steps (prescriptive)

1. Plan & size: Estimate concurrent capture needs (browsers × viewports × test frequency) to size worker pool and storage.
2. Prepare infra: Provision Kubernetes/VMs, object storage, DB, and networking (ingress, firewall, IdP).
3. Install: Deploy FullShot services (API, UI, workers) using provided Helm charts or installers.
4. Configure auth & RBAC: Connect SAML/OAuth, create roles and teams.
5. Integrate CI: Add pipeline steps or agents to trigger captures on PRs/commits.
6. Establish baselines: Run initial baseline captures for target branches/environments.
7. Tune thresholds & workflows: Set diff sensitivity, auto-approve rules, and notification routing.
8. Scale & monitor: Enable autoscaling for workers, monitor capture latency, storage usage, and error rates.
9. Train teams: Share review workflows, triage policies, and best practices for visual tests.

Best Practices

• Limit viewport matrix initially: Start with key breakpoints and browsers, expand coverage iteratively.
• Use visual test tags: Group tests by feature, page, or release to speed targeted runs.
• Keep baselines stable: Approve baselines from release builds, not from ephemeral feature branches.
• Prune screenshots: Implement retention policies to control storage costs.
• Parallelize smartly: Balance worker count with CI run costs and rate limits for external services.

Metrics to Track

• Mean time to detect regressions
• Average capture time per test
• Storage growth rate and cost
• Review/triage turnaround time
• False positive rate (diff noise)

Common Risks & Mitigations

• Flaky captures: Use stable test environments, deterministic data, and network controls.
• Storage bloat: Set retention, compress images, and purge old baselines.
• Performance bottlenecks: Autoscale workers and optimize capture scripts.
• Access misconfiguration: Enforce least-privilege RBAC and audit logs.