Relicx automatically generates AI-powered, smart tests to validate user in your CI/CD pipeline. A representative session is used to generate a test that exactly simulates the behavior of the end-user. Unlike, traditional e2e test authoring tools you do not need to do anything to create a test. Tests are created automatically and periodically refreshed as your user flow evolves.
You can also generate additional tests based on any user sessions by clicking the "Generate Test" button on the session replay page.
Relicx uses a highly intelligent test automation strategy to create ready-to-run, Smart tests that use AI/ML to navigate across application UI and data changes. These capabilities include
- Auto Tasks: Relicx test framework allows operations such as login, test setup, etc. to be automatically inserted into tests to eliminate manual editing and enable you to runs large number tests with minimal human inputs.
- Automatic Test Patamerization: Relicx tests are automatically parametrized to enable test execution across test environments with different data sets.
- Self-healing tests with Smart Selectors and Visual Locators: AI-powered Smart Selectors can intelligently navigate your application across UI changes. Unlike traditional brittle test automation, Relicx tests are highly stable and are designed not to break unless they will fail a human user as well.
- Auto Assertions and Validation to reduce false positives and negatives: Relicx automatically adds routine assertions to the generated tests to validate test execution success.
- Assert URL and Assert Title validate successful test navigation
- Auto Text Mutations Assertions: Relicx analyzes the flow sessions to identify common text mutations that follow a user action and then asserts these mutations while running tests.
- Relicx uses Robotic Process Automation (RPA) to test execution. Tests continue execution on error to validate as much of flow as possible. This reduces frivolous failures and reduces test automation noise.
While a session is very specific to an environment, the tests should be environment agnostic i.e. we should be able to execute it on any environment. When Relicx generates a test, it parametrizes all the inputs required to run a test on another environment. It is expected that the target environment will have the required data for the successful completion of the test. Usually, login credentials, general inputs on screens are all parameterized and are exposed in the test run screen at the time of execution.
Parameter values are defined per environment at test or test suite levels.
You can identify auto assertions in the test steps with the tick icons, as shown below
Additional assertions, if so desired but not required, can be added to the test using the edit test option
Automatic tasks are inserted in the test during the test execution based on pre-defined conditions. A common example is the-auto login task that must be executed prior to executing the test steps.
As stated above, Relicx does not solely reply test step completion as an indicator of a successful test. Instead, it scrutinizes each test run to look for backend API errors, page load performance issues, and visual differences. The screenshot below shows a test that encountered 504 API errors and visual locator discrepancies.
You can inspect each of these failures. Any expected changes or temporary issues can be "approved", following which the test run status changes to "Passed with Approval".