Quickstart
Create a project, write a test in plain language, and watch a real browser run it. Roughly ten minutes.
This guide takes you from signing in to your first passing test, written in plain language. No selectors, no code.
You'll need access to the Auretis dashboard and the URL of a web app you want to test. A public staging URL is easiest to start with.
1. Log in to the Auretis dashboard
Open the Auretis dashboard and sign in. Everything below happens there.
2. Create a project
A project is the container for one application you're testing. Click New Project and give it a name. A project only organizes your work. You set the app's URL later, on a test suite.
3. Add a regression and a test suite
Inside a project, tests live in a regression → test suite hierarchy. Create them in order:
Create a regression
A regression is a named set of suites, and it's what you run. Name it
something like Smoke tests.
Create a test suite and set its URL
The test suite holds the application's URLs. Its App URL is the base URL of the app under test. Its Start From URL is the page each test case opens at by default.
Point the App URL at a reachable URL, e.g. https://staging.example.com.
This is the simplest setup and works out of the box.
To test an app on your machine, expose it with a tunnel (e.g. a Cloudflare/ngrok URL) and use that as the App URL.
4. Write your first test case
A test case is one scenario. The fastest kind to start with is a Simple test case. You describe the whole goal in plain language, the way you'd explain it to a teammate, and the agent works out how to do it.
Go to /login, sign in with the demo email and password, and
confirm the dashboard shows the "Welcome back" greeting.The "confirm..." part is the assertion. That's the condition that has to hold for the test to pass, and everything before it is what the browser agent does.
Describe intent, not implementation. "The Sign in button" is more resilient than a CSS selector. When the markup changes, the agent still finds it.
Need finer control? An Advanced test case lets you compose explicit, reorderable steps (locate, act, assert) in the step builder. Either kind runs the same way.
5. Run it
Click Run. Auretis opens a real browser, runs the scenario, and checks the assertion. That single run is an execution. You can also run a whole suite or regression at once.
6. Read the result
When the run finishes, you'll see a pass/fail status, timing, and screenshots. On a failure, you also get a message explaining what went wrong, and for an Advanced case, the exact assertion that didn't hold.