Relicx allows you to add functional verifications to release validation using an interactive mode. These tests are page specific and are triggered when Relicx lands on a page during its autonomous exploration. These tests should be short and meant to test very specific functionality on a page. You can use these tests to ensure a button has a specific color or even make sure a certain transaction is working as expected. 

It is recommended that you do not create very long tests instead create many such tests to validate each functionality separately.

Benefits of Relicx Release Validation

Adding Tests to Release Validation

Running Release Validation

Relicx

Welcome to Relicx 🎉

Quick Introduction

Sign-up

Join an existing Org

Create your first Test

Create a login task

Setup Session Replay

Sandbox Quick Start

Untitled

User Actions

Assertions

Conditionals

Interactive Test Authoring

Step Descriptions

Editing Tests

Test Parameterization

Resilient Mode

Data Driven Tests

View Test Run Results

Test Errors and Severities

Running Tests

Natural Language Tests

Copilot Query Assertions

Copilot Auto Assertions

Relicx CoPilot

Test Suite

Application Discovery and Baselining

Generative AI-Powered Visual Validation

Automatic Release Validation

How Does Relicx Release Validation Work?

Interpreting the results

AUTOMATIC RELEASE VALIDATION

User Sessions

Session Replay and Detail

Session Errors

Developer Console

Generating Tests from User Sessions

Security and Privacy

Application & Environments

Adding Application

Adding a new Test Environment

Testing Firewall Protected Apps

Relicx Integrations

getSessionUrlCallback()

identify()

Log()

sessionVars()

sessionLabels()

Session Replay SDK

CI/CD Integration

Notifications

Email

Slack

Whitelisting IPs

Timezones

Importing tests into Relicx

Changelog

Adding Tests to Release Validation

Overview of creating a Functional Test