1. Docs
  2. Use cases
  3. Use cases
  4. How does SmartestQA learn what my application looks like?

How does SmartestQA learn what my application looks like?

SmartestQA learns your application in Discover: Discover Your App opens your app in a new tab and scans each page you visit for its interactive controls, and you review and save them as actions. The Action List holds every action with its locators, and the App Map describes each page: what it is for, where it leads and how well it is tested.

12 min read Updated CustomersAdmins

In short

On this page you can

  • Scan a web page into actions: one per control, with locators and a screenshot.
  • See every page as a record with its purpose, module, transitions and screenshots.
  • Find and fix controls and locators in one searchable Action List.
  • See per page how much of what users can do there is covered by a test.
  • Give the AI what it needs to write requirements and tests about your app.

How to use it

  1. Open Discover and click Discover Your App on Setup Roadmap.
  2. In the new tab, open a page and click Start Recording.
  3. Check the Page name in Review Actions and click Save Selected.
  4. Go through the other pages, then click Stop Recording.
  5. In App Map, click Update map, then write a Purpose for each page under Detail.

The short answer#

You show SmartestQA the application in Discover, the first item of the main menu. In a web project, Discover Your App opens your start page in a new tab; on each page you visit, the browser extension scans up to 400 interactive controls and works out locators for each. You review the list, name the page and save.

What it keeps has two views. The Action List holds every action: one control on one page, with a type, one or more locators, an optional Navigates To page and a screenshot. The App Map holds every page as a record: its purpose, preconditions, expected outcomes, risk, roles, screenshots, tasks and transitions. Analyze, AI test generation, Automate steps and AI assistants through MCP all read from here.

The problem this solves#

In many teams, what is known about the application is spread out. The locators sit inside test scripts. The description of each page sits in a shared document that is often out of date. Which pages have a test is kept in a spreadsheet, or in someone’s head.

That hurts in three places. The same button is located in several scripts, so one change in the page means several edits. Nobody can say quickly which pages have no test. And an AI that is asked to write tests knows nothing about the application, so it writes general steps. What is missing is one record of the pages and controls that tests, people and the AI all read.

An example#

This is an illustration, not a customer story. A team tests the web back office of a delivery app, and a tester starts with the three pages dispatchers use most.

  1. The tester chooses the Environment and the Start Page URL and clicks Discover Your App: “Recording started! Create actions in the new tab.”
  2. The tester logs in with a test user, opens the orders page and clicks Start Recording. The Review Actions window lists “38 actions found”. The tester checks the Page name, unticks the footer links and clicks Save Selected: “Page scanned! Navigate to other pages…”
  3. The tester opens the order detail page and the courier page. Each time the address changes, a new scan starts by itself. Then the tester clicks Stop Recording, and the Action List refreshes.
  4. In App Map the tester clicks Update map. The preview shows Pages to create and Transitions to create. The tester applies it: “Map updated”.
  5. Under Detail the tester writes a Purpose for each page, and adds a business rule about late orders as a note, one rule per note.
  6. After the first tests pass, the Tested column shows per page how much of what users can do there is covered by a test.

The team now has one list of controls that every test points at, and a page list that shows where tests are missing.

A shared document, page objects in your own scripts, and SmartestQA#

QuestionA shared documentPage objects in your own scriptsSmartestQA
Who collects the controls of a page?Nobody; the document describes pages in wordsA developer, one locator at a timeThe scan, on each page you visit, up to 400 controls per page; you review and save
Where does a locator live?Not in the documentIn code, which works well when one team owns all scriptsOn the action in the Action List; a step points at the action by its ID
What happens when a control changes?Someone updates the text, if they rememberYou edit the page object, and each copy of the locatorFix the locator once and every test that uses the action is fixed
Who writes what a page is for?A personUsually nobody; code comments at mostA person, under Detail; later Update map runs do not overwrite those text fields
Which pages have no test?Kept by hand, if at allYou search the scriptsThe Tested column shows it per page
What does an AI get when it writes tests?The document, if you paste itThe code, if it can read the repositoryEach page’s purpose, what can be done there, where it leads, and your notes

Steps#

  1. Have the basics ready

    A WEB project needs the SmartestQA extension in Chrome or Edge, a start page URL with an address for your environment, and a test user. See Connect your app. Mobile and desktop apps are captured through a running agent; see Mobile and desktop capture.

  2. Start Discover Your App

    Click the recording settings button and choose the Environment and the Start Page URL. Then click the purple Discover Your App button on Setup Roadmap, or Action ListMoreDiscover Your App.

    “Recording started! Create actions in the new tab.” Your start page opens in a new tab, with a panel at the bottom right.

  3. Scan a page

    Log in with your test user if needed, open the first page you want and click Start Recording in the panel. The extension scrolls the page to load lazy content, then scans the controls.

  4. Review and save

    The Review Actions window lists “n actions found”. Check the Page name (required, suggested from the address), untick anything you will never test, and click Save Selected. See How pages are named.

    “Page scanned! Navigate to other pages…”

  5. Move on through the app

    Open the next page. When the address changes, a new scan starts by itself after about a second. A dialog, a tab or a menu that adds two or more new controls is scanned on its own, under a derived page name. Click Stop Recording when you are done; the tab closes and the Action List refreshes.

  6. Update the map

    In App Map, click Update map. A preview shows Pages to create, Pages to update, Transitions to create and more. Apply it. The map builds pages from all actions and transitions from the step order of every test case. See Update map.

    “Map updated”.

  7. Describe the pages

    Click Detail on a page and fill Purpose, Preconditions, Expected outcomes, Risk and Roles. A good purpose names the user, the decision and the consequence. Your edits are protected: later Update map runs do not overwrite those text fields. See Describe a page.

  8. Group pages and add what no scan can see

    Move pages into modules with Add new module and the module drop-down on the row. Put business rules in Notes, one rule per note; notes are sent to the AI. See Group pages into modules and Notes.

What a scan creates#

Control on the pageAction typeExample name
Button, link, element with a clickable roleClickClick Submit Order
Editable input or text areaTypeType Email
Read-only inputGetGet Order Number
Drop-down selectSelect (by visible text)Select Country
  • Name: a verb plus the control’s visible label, at most 60 characters. When the project’s AI is on, the AI improves the names.
  • Locators: up to three XPath locators, each with a confidence score, or one CSS locator for controls inside a shadow DOM. Locators built on dynamic IDs, or that match more than one element, or that match nothing, are dropped.
  • Navigates To: filled in for links within the same site.
  • Screenshot: one cropped screenshot per control with the control outlined.
  • App Map record: address, page title, number of controls and the main screenshot.

How the App Map reads a page#

What you seeHow it is decided
VerifiedA page or transition seen in a passing test.
DeclaredA page or transition known only from Navigates To.
OrphanA page with neither.
Entry pageThe first page of the most passing test cases.
TestedCovered test points ÷ test points. Test points are the tasks on the page, its validation actions and the transitions leaving it.
Map colour≥ 80% green · 40–79% amber · < 40% red
“n unreachable”Visible pages that no action leads to, shown only when there are 2 or more.
CasesThe number of distinct test cases with a step that uses the action directly.

Example: checkout has 3 tasks, 2 validation actions and 2 transitions, so 7 points. Tests use the proof actions of 5 of them: 5 ÷ 7 = 71%, amber. Every formula is in How the numbers work.

Watch it#

The video shows the two results: the App Map with its modules, the page list, Detail, the Map view and Update map, then the Action List with its page pills, column filters, the unreachable chip and Auto-fix. It does not show the scan itself, Discover Your App.

Video transcript

The App Map is what the AI knows about your app: its pages, what you can do on each, and how they connect. On the left, pages are grouped into modules. Generating tests for a module uses only its pages. The list shows each page with its module and what can be done there. Detail opens the description of one page. Map draws the same pages as a graph, with the links between them. Update map rebuilds it from the actions Discover recorded. The Action List holds every action Discover recorded: the building blocks of your test steps. The page pills filter the list to one page of your application. Each column has its own filter: page name, action name, where it navigates to, and type. A row shows the action, its type, its locator, and in Cases how many test cases use it. The unreachable chip counts pages that no recorded action leads to. Auto-fix proposes the missing links. Edit, Duplicate and Delete are at the end of each row.

The App Map and the Action List: what SmartestQA knows about your app.

What you get#

  • One control, many tests. A test step points at an action by its ID. Fix a locator once and every test that uses the action is fixed.
  • Several ways to find each control. Recorded actions keep up to three locators with a confidence score each, so a run can fall back when one stops matching.
  • AI that writes about your app. When AI analyses requirements or generates tests, it receives each page’s purpose, preconditions, expected outcomes, risk, roles, what can be done there, where it leads, and your notes.
  • A view of what is untested. The App Map’s Tested column shows, per page, how much of what users can do there is covered by a test.
  • Usage counts. The Cases badge shows how many test cases use an action; click it to list them.
  • Modules shared across screens. A module groups pages of one business area, and Analyze creates one requirement folder per module.

Questions and answers#

Do I have to map every page of my application?Customers

No. Start with the pages of your three most important user flows. The Setup Roadmap counts Describe the app as done when 60% of the pages you have mapped have a purpose. See Setup Roadmap · Describe the app.

Does SmartestQA crawl my application by itself?Customers

Discover Your App scans the pages you visit: you open a page in the recording tab, and when the address changes a new scan starts by itself. You review what was found and save it page by page. See Step by step.

Can it scan pages behind a login?Customers

Yes. Log in in the tab Discover Your App opens, then click Start Recording on each page. Use a test user and test data, because a screenshot is stored with every action. See Can I scan pages behind a login?

Does the scan need AI?Customers

No. The scan and the locators work without AI. When the project’s AI is on, it improves the action names, and Update map can let the AI fill “What can be done here”, up to 60 pages per batch. See Does Discover Your App need AI?

What does a scan store, and where does the data go?Customers

The scan runs in the browser extension on your computer. It stores the controls, their locators and a screenshot of each control in your SmartestQA project. When AI is on, control labels are sent to the configured AI provider to name actions. See What data does a scan store or send?

Does it work for mobile and desktop applications?Customers

Yes, with other recorders. Discover Your App is for WEB projects. MOBILE projects use Record Actions with the Appium inspector, and DESKTOP projects use the Desktop Recorder; New Action works everywhere. See Mobile capture.

If I rename a page or an action, do my tests break?Customers

No. Steps point at actions by ID, not by name. A renamed page leaves its module and shows Not on map until you run Update map, and notes scoped to the old name need a new scope. See Renaming a page or an action.

Why do my recorded actions show XPath in amber?Customers

The locator chip is coloured by the type of the main locator, and the web recorder stores its locators as XPath. The recorder has already rejected dynamic and non-unique locators. Judge a recorded action by its last-run status and confidence, and add an id or name locator by hand where one exists. See Locator chip.

What happens if I skip Discover and only record tests?Customers

Recording in Automate still creates actions, so tests work. What you lose 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.

Can an AI assistant read or fill the App Map?Customers

Yes. An assistant connected through the SmartestQA MCP server reads Discover with the smartest_discover tool, can create or update actions with smartest_action_write and can fill page tasks. See For AI assistants (MCP).

Read more#

Didn’t find your answer?Write to support with your project name and what you see on screen.

info@smartestqa.ai