Discover Your App
Discover Your App opens your app in a new tab and scans each page you visit for its interactive controls. You review what it found, name the page and save.
In short
On this page you can
- Scan a web app page by page for its interactive controls.
- Review what each scan found and untick controls you will never test.
- Name pages well, using the rules behind the suggested names.
- See what a scan creates: action types, names, locators, screenshots, App Map record.
- Use Record Actions to capture only the controls you use.
How to use it
- Choose the environment and start page in the recording settings.
- Click Discover Your App, open your first page and click Start Recording.
- In Review Actions, check the Page name, untick noise and click Save Selected.
- Move through the app; each new page or dialog is scanned by itself.
- Click Stop Recording, then check Action List and App Map.
You need
A WEB project, the SmartestQA extension in Chrome or Edge, a start page URL with an address for your environment, and a test user. Set these up in Connect your app.
Step by step#
Check the recording settings
Click the recording settings button (it shows the environment, for example TEST · Login). Choose the Environment and the Start Page URL. Use Manage URLs to add one.
Start Discover Your App
Click the purple Discover Your App button on Setup Roadmap, or Action ListMoreDiscover Your App. SmartestQA says “Recording started! Create actions in the new tab.” and opens your start page in a new tab, with a panel at the bottom right titled Smartest · Discover Your App.
Go to the page and click Start Recording
Log in with your test user if needed and open the first page you want. Click Start Recording in the panel. The extension scrolls the page to load lazy content, then scans up to 400 interactive controls and works out locators for each.
Review what was found
The Review Actions window lists “n actions found”. Check the Page name (it is required and suggested from the address), untick anything you will never test, and look at the two special groups below.
Save Selected
Click Save Selected. The panel says “Page scanned! Navigate to other pages…”.
Move on through the app
Open the next page. When the address changes, a new scan starts by itself after about a second. When you open a dialog, a tab or a menu that adds two or more new controls, only the new controls are scanned, under a derived page name.
Stop Recording
Click Stop Recording. The tab closes and the Action List refreshes.
Each page you saved has its actions in the Action List and a record in the App Map with its address, title and a screenshot.
- How many controls the scan found on this page.
- Page name: required. Suggested from the address; change it if a better name exists.
- UPDATE: controls already saved on this page. Saving updates them and keeps their page name.
- Controls with no unique locator, typical for repeated row buttons. Untick them or fix them by hand later.
- Save Selected saves only ticked items.
How pages are named#
The suggested page name comes from the address. You can change it in the review window before saving.
| Address or screen change | Suggested page name | Rule |
|---|---|---|
https://shop.example.com/ | home | The root path becomes home. |
/customer-orders/8812 | customer_orders | Lower case, hyphens become _, a trailing numeric ID is dropped. |
/admin/user-roles | admin/user_roles | Path segments are joined with /. |
Tab “Billing” opened on settings | settings_billing | Tabs add _<label>. |
“Add user” button opens a dialog on users | users_add_user_modal | Open, add, create and edit triggers add _<label>_modal. |
Name pages the way your team talks
Page names are used in requirements, AI prompts and reports. checkout reads better than shop/cart/step_2. Rename in the review window, before the first save: once tests use a page, renaming it has side effects.
What a scan creates#
| Control on the page | Action type | Example name |
|---|---|---|
| Button, link, element with a clickable role | Click | Click Submit Order |
| Editable input or text area | Type | Type Email |
| Read-only input | Get | Get Order Number |
| Drop-down select | Select (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; without AI you still get the plain 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. Add, new and edit buttons that open a dialog get
<page>_modal. - Screenshot: one cropped screenshot per control with the control outlined. If cropping fails, the full page is used.
- App Map record: address, page title, number of controls and the main screenshot, marked as coming from the recorder.
Record Actions instead of a full scan#
MoreRecord Actions (“Record actions from browser”) captures only the controls you actually use while you click through the app, with a screenshot of each. Use it when a page has hundreds of controls and you need five, or when you want actions in the order of a real flow.
If something goes wrong#
Didn’t find your answer?Write to support with your project name and what you see on screen.
info@smartestqa.ai