Set a default URL, to be pre-filled in each test creation

I have a long domain name and it would be nice to set it once in a setting panel and have it pre-filled instead of having to type it in at each test creation.

Full page AI Visual Assertion

In some websites such as e-commerce websites we want to assert how product are displayed. In these cases we need the ability to use a full page visual assertion.

Possibility to import a reusable test, into a reusable test

Reusable tests are currently 1-level deep. It would be helpful to increase that limitation in order to support more advanced flows. For example: Test 1: I can login Test 2: I can create a test → uses test 1 + custom logic Test 3: I can run a test → uses test 1 + test 2 + custom logic

Add a DOM-based assertion

We can currently add visual assertions that work fine in most cases. However, we also need to assert the presence of a given element in the DOM using either an AI selector + Assertion description or a CSS Selector + an Assertion description. For example : - Element Description : The main page table - Assertion : It contains an element with id=”some-value”

Add Tags to tests

As a user, I would like to categorize or tag my tests in order to enhance the search experience.

Improve click on non-interactive elements

The main AI uses DOM analysis to choose which interactive element it will use for click actions. However, in many scenarios, websites don’t use standard interactive HTML elements and just use non-interactive elements such as. We need to find a fallback solution using CoVA techniques for these cases.

Export / Import tests as file

Having the possibility to write tests as a yaml or a json file could be a wonderful addition in order to add those tests in the same repository, and use it in the acceptance test phase of the deployment pipeline.

Get SMS verification code action

Allow to retry assertions

Sometimes we don’t know how long a process can be. It would be helpful to have the ability to configure a retry strategy for an AI visual assertion. Example usage: Assertion Description: The process is completed and shows a green screen Timeout after: 5 minutes This action would result in an exponential back off retry. After 5 minutes, the instruction would fail if not passed. If passed within the 5 minutes, the test continues.

Conditional flows

As a user, I want the possibility to trigger an instruction branch based on one condition. The condition could be expressed with an AI visual assertion. AI Visual Assertion: “If the product shows some surfboard, then trigger” - If true: trigger flow A - If false: trigger flow B

Evaluate custom javascript

Reload current page

Go to URL: possibility to open it in a new tab

Autopilot Testing Agent

We’re going to launch a very special action capable of testing a whole scenario by taking as argument a prompt mentioning the starting point and the expected result. This Autopilot mode will be especially helpful to fill in very long and non-deterministic forms, such as lead generation forms and much more.

Support for campaigns

The problem we’re facing: When we release a new version of a huge software, we generally want to run a bunch of suites and tests in parallel. Then, we want to aggregate the result data and statistics about the success and failure rate of this specific execution. The way we would like to solve it: By creating a campaign, a user would be able to run a given list of suites and then track the specific execution result for this campaign. Later we could potentially re-run the same campaign and track the new execution results to compare both of them.

Better support for Radio inputs

Radio inputs are tricky since their implementation differs on many websites. The Click Element action shows limitation in interacting with Radios so we need a dedicated action that is able to solve this problem.

CLI to launch test suites from a CI/CD

As part of the development process, it’s important to launch acceptance tests directly in a CI/CD pipeline. We need a simple and versatile CLI that DevOps can use in their pipeline to trigger a suite and listen for a suite-run result.

Support file upload

It would be nice to have a new action to support file upload :)

Reporting API

Many companies have internal dashboards gathering data from external services. We’ll make our reporting data accessible through an API so these companies will have the ability to make their own custom dashboards.

Manage multiple screen sizes

As a user I want the ability to test my application on many different device screens so I can verify how it works on Mobile, Tablet and Desktop.

Call a reusable test (or a flow) with variables in arguments

I want the ability to pass variables in the argument of my reusable test. A good usecase example is for a login flow. I want to script my login flow once but be able to call it with as many different usernames/passwords as I want to. The same login could be applied to a test launched from a CI/CD pipeline.

Organize tests with directories

We’ll add a better organization of the tests to organize them by directories and identify more clearly the distinction between reusable tests and others.

Support for native actions

For many reasons, it’s easier to use UI elements to describe the action we want to do. We need native actions such as: click element fill input check option

Improve click speed

Support Native Mobile Devices

HTTP Call Action

We need an action able to trigger an API HTTP Call. It’s useful to trigger logics such as teardown endpoints.