---
title: "How do I automate a web test without writing code?"
section: "Use cases"
description: "No-code web test automation in SmartestQA: install the browser extension, add a start page URL, record the flow in Automate, add an Assert step from the toolbar, dry run it and read the live log. Steps, limits and common questions."
url: https://docs.smartestqa.ai/en/use-case-no-code-web.html
audience: [customer, admin]
updated: 2026-11-12
keywords: "no-code test automation codeless web testing record and playback automate web test without coding without programming browser extension recorder chrome edge record test steps add assertion without code dry run low-code ui test manual tester automation manual testing vs test scripts vs no-code tester without programming automate hr portal example record a test instead of scripting"
---
# Use cases: How do I automate a web test without writing code?

In SmartestQA you record a web test instead of writing it: click Record in Automate, do the flow in your app in a new tab, and the browser extension adds every click, typed value and selection as a step. You then add a check with Assert from the step toolbar and try the test with Dry Run.

## In short

**On this page you can**

- Record clicks, typed values and selections in Chrome or Edge as test steps.
- Add checks, API calls, database queries and mail steps from the step toolbar, without code.
- Compare a value with what you expect, using one of ten assertion types.
- Try the test with a dry run and watch every step live, with a screenshot.
- Reorder, switch off, remove or rebind steps in the editor.

**How to use it**

1. Install the SmartestQA browser extension and add a start page URL in Configuration › Project Panel › Start Page URLs .
2. In Automate click New Test Case , pick the start page URL and the environment.
3. Click Record , do the flow in the new tab, close the tab and come back.
4. Add an Assert step at the end and click Save .
5. Click Dry Run , choose Run on Server or Run on your Agent and read the live log.

## The short answer

You do not write a script. In a SmartestQA web project you open a test case in **Automate**, click **Record** and use your application in a new browser tab. The SmartestQA extension for Chrome and Edge adds every click, typed value and selection as a step, and creates one action per control with its locators and a screenshot. When you close the tab, the steps are in the test case.

What you cannot click, you add from the step toolbar: a check with [**Assert**](https://docs.smartestqa.ai/en/automate-steps-assertions.html#assertion-step), an [**API**](https://docs.smartestqa.ai/en/automate-steps-api.html#add-api-step) call, a [**Database**](https://docs.smartestqa.ai/en/automate-steps-database.html#add-db-step) query, a [**Mail**](https://docs.smartestqa.ai/en/automate-steps-mail.html#add-mail-step) step. [**Dry Run**](https://docs.smartestqa.ai/en/automate-dry-run.html#start-dry-run) then runs the saved test once and shows each step live with a screenshot. Code steps ([**Python**](https://docs.smartestqa.ai/en/automate-steps-code.html#add-code-step), [**JS**](https://docs.smartestqa.ai/en/automate-steps-code.html#add-code-step)) exist for what no step type covers.

## The problem this solves

In many teams the people who know the application best are testers and business users who do not write code. They check the important flows by hand before each release, and they repeat the same clicks every time. The checks depend on who has time, and nothing records what was checked.

Automating a flow usually means a script, so it waits for a developer or a test engineer. When a page changes, the script waits for that person again. What is missing is a way for the person who knows the flow to turn it into a test that runs again, and to see it run.

## An example

This is an illustration, not a customer story. A team runs an HR portal, and a tester who has never written a script wants to automate the flow “submit a leave request”.

1. The tester installs the SmartestQA extension in Chrome. A start page URL with a **TEST Environment URL** for the portal is added under [**Start Page URLs**](https://docs.smartestqa.ai/en/quick-start-connect.html#start-page-url).
2. In **Automate** the tester clicks [**New Test Case**](https://docs.smartestqa.ai/en/automate-test-cases.html#create-test-case), picks the start page URL and the environment, and clicks **Record**. The portal opens in a new tab. The tester logs in with a test user, fills in the leave request, submits it and closes the tab. SmartestQA shows “9 new step(s) added!”.
3. The flow is recorded, but nothing is checked yet. The tester adds a step with an action of type Get that stores the confirmation message, then clicks [**Assert**](https://docs.smartestqa.ai/en/automate-steps-assertions.html#assertion-step), chooses the type Contains and sets the expected value `submitted`.
4. The tester names the test case, clicks **Save**, then [**Dry Run**](https://docs.smartestqa.ai/en/automate-dry-run.html#start-dry-run) and [**Run on Server**](https://docs.smartestqa.ai/en/quick-start-connect.html#agent). The [**Test Run**](https://docs.smartestqa.ai/en/automate-dry-run.html#live-log) panel opens with the live log and a screenshot for every step. It ends with “Test completed successfully!”.
5. A dry run is not stored in a report, so the tester adds the test case to a pipeline in **Schedule** and clicks [**Save & Execute**](https://docs.smartestqa.ai/en/quick-start-first-test.html#step-6). The result is now in **Report**.

The person who knows the flow built the test, and no script was written.

## By hand, with hand-written test scripts, and with SmartestQA

| Question | Checked by hand | Hand-written test scripts | SmartestQA |
| --- | --- | --- | --- |
| Who can build the test? | Anyone who knows the application | Someone who can program | Anyone who can do the flow in Chrome or Edge with the extension installed |
| How does a click become a step? | It does not; a person clicks again each time | You write a locator and a command for each control | The recorder adds every click, typed value and selection as a step |
| How is the result checked? | By eye, which works well for a new or rarely used flow | With an assertion in code | With an [**Assert**](https://docs.smartestqa.ai/en/automate-steps-assertions.html#assertion-step) step that compares a saved value with the expected one |
| What do you see while it runs? | The application itself | What the script logs | A live log, with a screenshot for every step of a dry run |
| Where does it run? | On the tester’s machine | On a machine or CI runner you set up | [**Run on Server**](https://docs.smartestqa.ai/en/quick-start-connect.html#agent), headless with no agent, or [**Run on your Agent**](https://docs.smartestqa.ai/en/quick-start-connect.html#agent) on your computer |
| What if no ready-made step fits? | The tester does it by hand | You write more code, with full control | [**Python**](https://docs.smartestqa.ai/en/automate-steps-code.html#add-code-step) and [**JS**](https://docs.smartestqa.ai/en/automate-steps-code.html#add-code-step) code steps exist for that case |

## Steps

1. **Install the browser extension**

   Open SmartestQA in the Chrome Web Store and click [**Add to Chrome**](https://docs.smartestqa.ai/en/quick-start-connect.html#install-extension). The same listing works in Edge. Then press F5 on every SmartestQA tab that was already open: a newly installed extension cannot talk to tabs that were open before it. See [Install the browser extension](https://docs.smartestqa.ai/en/quick-start-connect.html#install-extension).
2. **Add a start page URL**

   Go to **Configuration** › **Project Panel** › [**Start Page URLs**](https://docs.smartestqa.ai/en/quick-start-connect.html#start-page-url) and click **+ Add**. Give it a **Name** and at least one of **DEV Environment URL**, **TEST Environment URL**, **PRP Environment URL**. Addresses must start with `http://` or `https://`. See [Add a start page URL](https://docs.smartestqa.ai/en/quick-start-connect.html#start-page-url).
3. **Open a test case and pick where it starts**

   Go to **Automate** and click [**New Test Case**](https://docs.smartestqa.ai/en/automate-test-cases.html#create-test-case). In [**Test Case Detail**](https://docs.smartestqa.ai/en/automate-editor.html#test-case-detail) pick the start page URL and the environment. Without a start page, recording does not start: “Please select a Start Page URL.” See [Environment and start page](https://docs.smartestqa.ai/en/automate-editor.html#environment).
4. **Record the flow**

   Click **Record** at the left of the step toolbar. Your app opens in a new tab. Log in with a test user and work through the flow the way a user would. Wait for each page to load before you click. Then close the recording tab and return to SmartestQA.

   “n new step(s) added!” The new steps are appended at the end of the list. Each one points at an action in Discover.
5. **Add a check**

   A test proves something only when it checks a result. Click [**Assert**](https://docs.smartestqa.ai/en/automate-steps-assertions.html#assertion-step) in the toolbar; the dialog [**Add Assertion/Verify**](https://docs.smartestqa.ai/en/automate-steps-assertions.html#assertion-step) opens. Fill **Page Name**, [**Assertion Type**](https://docs.smartestqa.ai/en/automate-steps-assertions.html#assertion-types) and [**Test Step Name**](https://docs.smartestqa.ai/en/automate-editor.html#rename-step), click **Add**, then set actual and expected in the right panel. An assertion compares values and does not read the page, so save the value first with an action of type Get. See [Add an Assertion step](https://docs.smartestqa.ai/en/automate-steps-assertions.html#assertion-step).
6. **Name and save**

   Give the test case a name and click **Save**. You do not have to write a description: the AI writes one from the steps. There is no autosave. See [Save](https://docs.smartestqa.ai/en/automate-editor.html#save).

   “name updated successfully”.
7. **Dry run it**

   Click [**Dry Run**](https://docs.smartestqa.ai/en/automate-dry-run.html#start-dry-run), just left of **Save**, and choose the run target: [**Run on Server**](https://docs.smartestqa.ai/en/quick-start-connect.html#agent) (headless, no agent needed) or [**Run on your Agent**](https://docs.smartestqa.ai/en/quick-start-connect.html#agent) (on your computer; you can watch the browser). See [Web projects](https://docs.smartestqa.ai/en/automate-dry-run.html#web-targets).

   “Test execution started successfully” and the [**Test Run**](https://docs.smartestqa.ai/en/automate-dry-run.html#live-log) panel opens with the live log. It ends with “Test completed successfully!” or “Test failed”.
8. **Keep the result**

   “Dry Run results are not saved to reports.” For a result you can keep and share, go to **Schedule**, create a pipeline, add the test case and click [**Save & Execute**](https://docs.smartestqa.ai/en/quick-start-first-test.html#step-6). Then open **Report**. See [Run it and read the report](https://docs.smartestqa.ai/en/quick-start-first-test.html#step-6).

## Steps you can add without code

These are buttons of the step toolbar in a WEB project that need no code. The full list is in [The step toolbar](https://docs.smartestqa.ai/en/automate-add-steps.html#toolbar).

| Button | Adds | Good to know |
| --- | --- | --- |
| **Record** | A recorded flow: clicks, typed values, selections | Web recording saves at once, as you record. |
| **Action** | A step bound to an existing action | The **Action List** dialog stays open, so each click adds one step. |
| **Template** | A template test case as one step | Change the template and every test case that uses it changes too. |
| [**Assert**](https://docs.smartestqa.ai/en/automate-steps-assertions.html#assertion-step) | A comparison of an actual value with an expected one | A failed assertion stops the test case. |
| [**AI step**](https://docs.smartestqa.ai/en/automate-steps-ai.html#add-ai-step) | A step written in plain language that the AI performs, answers or checks | Calls the AI on every run: slower, not deterministic, and needs AI turned on. |
| [**API**](https://docs.smartestqa.ai/en/automate-steps-api.html#add-api-step) | An HTTP request, with values extracted from the response | Any HTTP status passes the step; extract `@status` and assert it if the code matters. |
| [**Network**](https://docs.smartestqa.ai/en/automate-steps-network.html#add-network-step) | A check of the browser’s own network calls | WEB projects only. |
| **More…** › [**Database**](https://docs.smartestqa.ai/en/automate-steps-database.html#add-db-step) | A SELECT query whose columns become variables | The query runs from where the test runs. |
| **More…** › [**Mail**](https://docs.smartestqa.ai/en/automate-steps-mail.html#add-mail-step) | Read mails, extract an OTP or link, send or wait for a mail | Reads only unread mails that arrived shortly before or after the step starts. |

## The ten assertion types

The [**Assertion Type**](https://docs.smartestqa.ai/en/automate-steps-assertions.html#assertion-types) list shows the types set up for your installation. By default these ten. Text is compared case-sensitive and is not trimmed; see [How values are compared](https://docs.smartestqa.ai/en/automate-steps-assertions.html#comparison-rules).

| Type | Passes when | Example (actual → expected) |
| --- | --- | --- |
| Equals | The values are exactly equal. | Paid → Paid |
| Not Equals | The values are not equal. | Draft → Paid |
| Contains | The value includes the expected text. | Order 1042 created → created |
| Not Contains | The value does not include it. | Saved → Error |
| Starts With | The value starts with the expected text. | INV-2026-17 → INV- |
| Ends With | The value ends with the expected text. | report.pdf → .pdf |
| Is Empty | The value is empty or blank. | No expected value |
| Is Not Empty | The value is not empty. | No expected value |
| Greater Than | The value is a number greater than expected. | 1234.5 → 1000 |
| Less Than | The value is a number less than expected. | 850 → 2000 |

## What you get

- **A test case built from what you did.** One step per click, typed value and selection, each linked to an action with locators and a screenshot.
- **Checks without code.** Ten assertion types by default, plus a Visibility Check action that verifies an element or a text is visible on the page.
- **A live log.** One row per active step with a status badge, messages, duration and a screenshot; dry runs take a screenshot for every step.
- **Two places to try it.** [**Run on Server**](https://docs.smartestqa.ai/en/quick-start-connect.html#agent) runs headless with no agent; [**Run on your Agent**](https://docs.smartestqa.ai/en/quick-start-connect.html#agent) opens a visible browser on your computer.
- **An editor for the steps.** Drag to reorder, **Deactivate** a step, **Remove** it, or bind it to another control with [**Replace Action**](https://docs.smartestqa.ai/en/automate-editor.html#replace-action).
- **Reuse.** A recorded action can be added to any other test case with **Action**, and a template test case can be added as one step with **Template**.
- **Locator repair.** When all locators of a control fail in a run, auto-heal looks for the control; if it finds it, a review is created in Maintenance.

## Questions and answers

### Q: Do I need to know programming to automate a web test in SmartestQA?

No. You record the flow with **Record** in Automate and add checks, API, database and mail steps from the step toolbar. [**Python**](https://docs.smartestqa.ai/en/automate-steps-code.html#add-code-step) and [**JS**](https://docs.smartestqa.ai/en/automate-steps-code.html#add-code-step) steps are there for what no step type covers, and you can leave them out. See [Which step family to use](https://docs.smartestqa.ai/en/automate-add-steps.html#step-families).

_Audience: customer, admin_

### Q: Which browsers can I record in?

Chrome and Edge. The SmartestQA extension is installed from the Chrome Web Store with [**Add to Chrome**](https://docs.smartestqa.ai/en/quick-start-connect.html#install-extension), and the same listing works in Edge. Without the extension, **Record** opens the Web Store instead of your app. See [Install the browser extension](https://docs.smartestqa.ai/en/quick-start-connect.html#install-extension).

_Audience: customer, admin_

### Q: Do I have to install anything besides the browser extension?

Not for a web app that is reachable from the internet: [**Run on Server**](https://docs.smartestqa.ai/en/quick-start-connect.html#agent) runs headless on the Smartest Server and needs no agent. You need an agent when you want to watch the browser during a run, or when the app is behind a VPN, a firewall or on an intranet. See [Do you need an agent?](https://docs.smartestqa.ai/en/quick-start-connect.html#agent)

_Audience: customer, admin_

### Q: How do I check that the page shows the right result, without code?

Read the value with an action of type Get, which stores the text under a key you name, then add an [**Assert**](https://docs.smartestqa.ai/en/automate-steps-assertions.html#assertion-step) step that compares it with the expected value, for example Contains `saved`. To verify only that an element or a text is visible, use an action of type Visibility Check. See [Common patterns](https://docs.smartestqa.ai/en/automate-steps-assertions.html#patterns).

_Audience: customer, admin_

### Q: Can I record a test that starts with a login?

Yes. Log in in the recording tab and go on with the flow. Use a test user: the values you type are stored in the steps, and recording saves a screenshot of every control you use. Values typed into fields named like password or token are masked in run logs but still stored in the step, so put real secrets in a data source. See [Secrets](https://docs.smartestqa.ai/en/data-source-secrets.html).

_Audience: customer, admin_

### Q: Can I change the steps after recording?

Yes. In the editor you drag a step to reorder it, use **Deactivate** to leave it out of every run, **Remove** to delete it, and [**Replace Action**](https://docs.smartestqa.ai/en/automate-editor.html#replace-action) to bind it to another control. Typed values are changed in [**Parameters List**](https://docs.smartestqa.ai/en/automate-editor.html#step-parameters). These changes are kept when you click **Save**. See [Change steps](https://docs.smartestqa.ai/en/automate-editor.html#edit-steps).

_Audience: customer, admin_

### Q: Are recorded steps saved automatically?

Steps recorded with the web extension are saved at once, while you record. Everything else you change in the editor is saved only when you click **Save**; there is no autosave and no keyboard shortcut for it. See [What is saved without Save](https://docs.smartestqa.ai/en/automate-editor.html#saved-at-once).

_Audience: customer, admin_

### Q: Does a dry run give me a report?

No. A dry run shows a live log, and its screenshots are deleted after 1 hour. A pipeline run from **Schedule** is stored in Report with screenshots, video and logs. See [Run modes: dry run, pipeline, agent](https://docs.smartestqa.ai/en/automate-dry-run.html#run-modes).

_Audience: customer, admin_

### Q: What do I do when a recorded step fails?

Open the first red step in the live log; later steps are usually SKIPPED because of it. Read the message, look at the screenshot, change the value, the wait, the order or the locator, save and dry run again. See [Diagnose a failed step](https://docs.smartestqa.ai/en/automate-dry-run.html#read-a-failure).

_Audience: customer, admin_

### Q: Do I have to map my application before I record a test?

No. Recording in Automate creates the actions its steps use, so the test works. What you lose without Discover is context: the App Map has no purposes or coverage, and AI-generated requirements and tests know only the names of controls. See [Why spend time here](https://docs.smartestqa.ai/en/discover.html#why).

_Audience: customer, admin_

## Read more

- [Connect your app](https://docs.smartestqa.ai/en/quick-start-connect.html): the extension, start page URLs and when you need an agent.
- [Record a web flow](https://docs.smartestqa.ai/en/automate-add-steps.html#record-web): every message the recorder can show.
- [Choose the right check](https://docs.smartestqa.ai/en/automate-steps-assertions.html#choose-a-check): Assertion, Visibility Check, AI Check and Network Check compared.
- [Read the live log](https://docs.smartestqa.ai/en/automate-dry-run.html#live-log): the badges and what each one means.
- [Discover Your App](https://docs.smartestqa.ai/en/discover-your-app.html): scan whole pages into actions before you build tests.
- [What happens to my tests when the UI changes?](https://docs.smartestqa.ai/en/use-case-self-healing.html): how a broken locator is repaired.
- [How do I build, run and schedule a regression suite?](https://docs.smartestqa.ai/en/use-case-regression.html): put the recorded tests in a pipeline.
