In Review

Planned

In Progress

Completed

Main Roadmap

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

Possibility to import a reusable test, into a reusable test

Kevin Piacentini

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.<img src="https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/0191b7ba-03e9-716d-a303-469e905a2902.png" data-width="100%" data-align="left">

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

ilios Galil

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 a DOM-based assertion

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

Add Tags to tests

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 &lt;div&gt;. We need to find a fallback solution using CoVA techniques for these cases.

Improve click on non-interactive elements

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.

Organize tests with directories

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.

Export / Import tests as file

Pierre Criulanscy

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.

Allow to retry assertions

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.

Reporting API

Support Native Mobile Devices

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.

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

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

Conditional flows

Right click action

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.

Full page AI Visual Assertion

Get SMS verification code action

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.

CLI to launch test suites from a CI/CD

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

HTTP Call Action

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.

Manage multiple screen sizes

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

Support file upload

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

Support for native actions

A simple action that simulates a mouseover on a given element.

Hover element action

As a user I want the ability to send a Key Event. This is useful for search input or autocomplete input that have no search button. Here’s the list of the most used keys: KeyEvent.VK_ENTER KeyEvent.VK_ESCAPE KeyEvent.VK_TAB KeyEvent.VK_BACK_SPACE KeyEvent.VK_DELETE KeyEvent.VK_SHIFT KeyEvent.VK_CONTROL KeyEvent.VK_ALT KeyEvent.VK_SPACE KeyEvent.VK_UP KeyEvent.VK_DOWN KeyEvent.VK_LEFT KeyEvent.VK_RIGHT KeyEvent.VK_F1 à KeyEvent.VK_F12 KeyEvent.VK_HOME KeyEvent.VK_END KeyEvent.VK_PAGE_UP KeyEvent.VK_PAGE_DOWN KeyEvent.VK_A à KeyEvent.VK_Z KeyEvent.VK_0 à KeyEvent.VK_9

Send Key Action

Many companies need to whitelist fixed IPs in order to test internal products. We plan to provide a range of public fixed IP addresses you can authorize.

Fixed IP range

When create multiple similar tests, it would be nice to be able to duplicate a test and modify it from there.

Duplicate a test

As a user, I will be able to configure multiple recipients who can be alerted by email when a test fails. Later, more Notification Drivers will be available. Feel free to open a new feature request for other drivers.

Email alerting when a test fails

When updating the Start URL and a test description right away, it seems a race condition prevents the Start URL for being saved.

Race condition issue when updating the start url

We need the ability to store variables and secrets we can reuse across tests and suites.One obvious use case is to store usernames and passwords to complete a login flow.

Support for variables and secrets

Help Center

Improved

Fixed

Admin

Manager

Contributor

magicinspector

Rejected

Postponed

High Priority

Low Priority

Quarterly Roadmap

Monthly Roadmap

Let us know what you want our team to work on, and we’ll include it in our roadmap.

Magic Inspector

Main Roadmap