Getting Started

This walkthrough takes you from a new account to a completed test session. It assumes you've already signed up at app.devassure.io — new accounts start on a 7-day free trial with pre-provisioned Cloud Agents, so there's nothing to install first. Paid plans are $25 per agent per month with unlimited executions; see Pricing.

1. Create an environment

An environment tells O2 what to test.

1. In the left navigation, select Environments.
2. Click Add Environment (top right).
3. Provide:
   • Name — a short, memorable label (e.g. production, staging, checkout). This is how the environment appears throughout the app, including in test session rows.
   • URL — the base URL O2 should load when a test case says load the url (e.g. https://app.yourproduct.com/login).
4. Save. The environment now appears on your Dashboard with an initial health score, and is selectable from the test case editor and test session launcher.

tip

Create one environment per meaningfully distinct target — for example, separate production and staging environments, or split a large app into checkout and account-settings if you want independent health scores per flow.

2. Write your first test case

Test cases in DevAssure are written as plain-English steps — no CSS selectors, no XPath, no code.

1. Select Test cases in the left navigation.

2. Click Add Test Case.

3. Choose or create a folder to organize it under (e.g. /airbnb, /checkout) — folders group related test cases and are also usable as filters later.

4. Give the test case a short title (e.g. search) and set a Priority (P0–P3) if you use priority to triage failures.

5. Add Tags if you want to filter or report on this test case later (e.g. smoke, regression).

6. Under Steps, write each action on its own line, in the order it should happen. For example:

   1. load the url
   2. enter a destination
   3. add dates
   4. add guests
   5. click on search
   6. validate the search results are inline with the data entered

   Write steps the way you'd explain them to a new tester. O2's agent interprets each line against the live page — locating the right element by context, not by a hardcoded selector — so the test case keeps working even after a UI redesign changes the underlying markup.

7. Save the test case.

3. Run it on a Cloud Agent

1. Open the test case and click Run, or go to Test sessions → New Test Session to run one or more test cases together.
2. Select the environment to run against.
3. Confirm and start. A Cloud Agent is provisioned automatically — there's no queue to configure and nothing to install locally.
4. Watch the session move from Running to Completed in the Test sessions list. Click into it for a full breakdown: score out of 100, per-step results, duration, and which agent executed it.

4. Where to go next

• Environments — health scoring and managing multiple targets.
• Agents — how many agents you have, parallelism, and self-hosted agents.
• Test Sessions — reading results, statuses, and scores.
• Scheduling & CI/CD — running on a cron or from your pipeline.