Testing Capabilities
The platform supports multiple test types to cover different needs - from lightweight availability checks to full end-to-end user journeys. Each test can also be executed from different locations, which helps you verify how your website behaves for users in different regions.
At the moment, only web testing is available, with more capabilities planned over time.
Choose the Right Test Type
Section titled “Choose the Right Test Type”Use the test type that matches the question you want answered:
- Choose Website Scenario when you need to validate a full user journey such as login, checkout, or form submission.
- Choose Website Availability when you want a fast signal that the website is reachable, returns the expected HTTP status, and passes technical checks such as SSL validation.
- Choose Website Vitals when you want to track performance quality over time using thresholds for Web Vitals and Lighthouse scores.
Comparison at a Glance
Section titled “Comparison at a Glance”| Test Type | Best for | Speed | Main signal | Typical alert reason |
|---|---|---|---|---|
| Website Scenario | End-to-end user flows | Slowest | Functional and visual behavior | A user step fails, content is wrong, or the UI changes unexpectedly |
| Website Availability | Fast technical health checks | Fastest | Reachability, HTTP status, and SSL checks | The website is down, returns an unexpected status, or has an SSL problem |
| Website Vitals | Performance monitoring | Medium | Web Vitals and Lighthouse thresholds | LCP, CLS, TBT, TTI, or score thresholds regress |
Common Monitoring Setups
Section titled “Common Monitoring Setups”Most teams get the best coverage by combining test types instead of relying on only one.
Recommended Baseline
Section titled “Recommended Baseline”- Run Website Availability frequently for a fast canary signal.
- Run Website Scenario for critical business paths such as sign-in, checkout, lead capture, or account creation.
- Run Website Vitals daily or after releases to catch performance regressions before they affect users.
- Use multiple locations when geography matters, such as regional outages, CDN issues, or location-specific performance differences.
Example Use Cases
Section titled “Example Use Cases”- A deployment breaks the login flow: use Website Scenario.
- A landing page stops loading from a public location: use Website Availability.
- An SSL certificate is close to expiry or misconfigured: use Website Availability.
- A page works in one region but fails or slows down in another: run the test from multiple locations.
- A release causes slower rendering or layout instability: use Website Vitals.
Website Tests
Section titled “Website Tests”Related Analysis Tools
Section titled “Related Analysis Tools”These features help you investigate failures, reduce false positives, and understand what changed during a run:
- Pixel Comparison detects visual regressions that code-level checks can miss.
- Performance Audit captures request timing and HAR data for deeper investigation.
- Page Structure Flexibility helps keep scenario tests resilient on dynamic frontends.
- Session Player lets you replay and compare runs when a scenario fails.
Current Scope
Section titled “Current Scope”Today, this page covers web testing capabilities only.
That means TestCLIX is currently designed for:
- website uptime, HTTP status, and SSL checks,
- browser-based end-to-end journeys,
- visual regression detection,
- and web performance monitoring.
If your goal is complete coverage, a practical starting point is one fast availability check, one or two critical scenarios, and a scheduled vitals test for your most important pages.