- Docs
- Get started
- Video library
Video library
Watch one lesson per module, or jump to a short video on the page that explains it. Every video has English narration and captions.
In short
On this page you can
- Watch one lesson per module, in menu order.
- Find the short video for one task.
- Start with the two-minute tour of the product.
How to use it
- Pick a module under Module training and press play.
- Use Short videos by module to open the page that explains a task.
- Turn on captions in the player if you prefer to read.
Module training#
One video per module, in the order of the main menu. Each one joins the short videos of that module into a single lesson. For a two-minute tour of the whole product, start with SmartestQA at a glance.
Discover#
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.
Analyze#
Video transcript
The tree starts at the project and has one folder per module, marked M, with a count. Open a module and select a main requirement. Its details open beside the tree: status, severity, dates, linked test cases and comments. Assessment (AI) is the next tab. Further down are the documents: specs and notes that AI generation reads. More adds a folder or a new document. Filter By Tags narrows the tree. Archive holds what you removed, until you restore it. New Requirement adds an empty requirement to the tree and opens it. Name it after what the user can do. In Description, say who it is for and what they get. Add opens a sub-requirement: one rule, written so that it can be tested. Add one for each rule, including what must not happen. Generate proposes sub-requirements with AI from the name and description. Save. The requirement takes its name in the tree, with its sub-requirements listed. A sub-requirement is one rule. Select it to see its details on the right. Test Cases lists what proves this rule. Nothing is linked yet. Add opens the test cases of the project. Add the cases that check this rule: here, two tests of the reset form. They now show under the sub-requirement, and their results count for it.
Automate#
Video transcript
Automate opens on the project summary: how many test cases passed, fail, or never ran. Condition coverage counts the conditions of your pages that a test really checks. What it tests lists each page, its test cases and its coverage. Gaps names the conditions no test covers yet, page by page. Transitions never tested are the links between pages that no test has followed. Trust warnings point at weak tests: no proof step, AI steps, not in a pipeline, or no requirement. A test case is a list of steps. Before it goes into a pipeline, try it with a dry run. Dry Run asks where to run: on the server, headless with nothing to install, or on your own agent. Dry run results are not saved to reports. The Test Run panel follows the run live: progress, and a status for every step. When it ends, every step shows its result.
Schedule#
Video transcript
Schedule lists every pipeline with its test cases, run environment and last result. New Pipeline creates an empty pipeline and opens it. Name it after what it proves. Add Test Case opens the project's test cases. Tick Log in as test user: it will be the Setup. Filter the tree to find the rest: three cases that add, edit and delete a note. Tick all three. The counter now shows four cases selected. Select a case to preview its steps before you add it. Add to pipeline puts the ticked cases into the run list. Every row starts as a normal Test. Hover a row and click its phase chip. Setup runs once at the start. Before and After wrap every test. Teardown runs once at the end. The login becomes Setup: if it fails, the tests are skipped. The delete case becomes Teardown. Teardown always runs, so the note is cleaned up even after a failure. Same session: the case continues in the previous case's browser. No new browser, no start page. Turn it on for every case that should carry on where the login left off. The run list now reads: Setup, two tests, Teardown, all in one browser session. Run on Server needs no setup: the first free server in the shared pool takes the run. Save & Execute saves the pipeline and starts the run. The run is queued, then the report opens on its own. Test Execution Logs follow the run live: the queue, the opened page, then each step. Every step lands in the log as it runs, until the Teardown finishes. Find the pipeline, hover its row and click Run. Run queues the pipeline and opens its report as soon as it starts. Back in Schedule, Last Run Date shows Running, with Stop run beside it. Stop run asks first: the running case finishes, the rest are skipped, and Teardown still runs. The cell shows Stopping until the run ends. Open the pipeline and click History for every past run, with result and status. A new pipeline runs on demand: its Period is Real-time. Open Period to schedule it: Daily, Weekly, Monthly or a cron expression. Choose Daily. The date fields become editable. Start Date Time is the first run, and its time is the time of every run. Here: 02:00. End Date Time is when the schedule stops: at most one year ahead. Save. From now on the pipeline starts by itself every night. Scheduled Runs lists every scheduled pipeline with its period and Next run, in your own time.
Report#
Video transcript
When the run is done, open it from Report. Four of four passed. The summary shows the verdict, the duration and one row per test case. Each case has its own tab, in run order: Setup first, Teardown last. Open a case to read every step, with its timing and a screenshot. Click a step for the detail: status, timings, log message and what the browser showed. The Teardown ran last and deleted the note the tests created. Report lists every run: pipeline, where it ran, duration, result and status. A red result means at least one test case failed. Open that run. The summary gives the verdict and counts what passed, failed and did not run. The test cases table shows each result with its failure reason. Open the failed case: its tab lists every step with status, timing and a screenshot. Click the failing step for its log detail and what the browser showed. AI Failure Analysis says whether the product, the test or the environment is to blame.
Tasks#
Video transcript
Tasks is a board with one column per status: Open, In Progress, Resolved and Closed. A card shows the name, the priority and the task number. List shows the same tasks as a table, with status, priority, type and who reported them. Back on Kanban, open a task. The detail holds the description, the members, attachments and the comments of the team. Close it and the board is where you left it. Tasks holds the defects of the project: found by failed runs, or reported by hand. New Task opens an empty task. Name it after what is wrong, not after where you saw it. Type, Priority and Status start as Functional Bug, Medium and Open. Raise the priority if it blocks users. In Description, write the steps, what you expected and what happened. Save. The task appears in the Open column with its priority and number. Open the card to add members, attachments and comments.
API Requests#
Video transcript
API Requests is the request library of the project, with one folder per module. Each request carries its method: GET, POST, PUT or DELETE. A folder can hold requests for one flow, such as login with good and bad credentials. Select a request to open it in the editor. Set the URL and the body. Values can come from Data Center keys and datasets. Send tries the request and shows the response underneath. Save keeps it for your tests. Authorization, parameters and headers are on the right. A request can inherit them from its folder. New Request adds one by hand; More imports a whole API description.
Short videos by module#
Each short video sits on the page that explains its subject.
| Module | Video | Length |
|---|---|---|
| Autonomous Agents | Review an agent run | 0:42 |
| Analyze | Organise the requirement tree | 0:38 |
| Analyze | Write a requirement | 0:41 |
| Analyze | Link test cases to a requirement | 0:26 |
| Automate | Dry run a test case | 0:35 |
| Use cases | Prove every requirement is tested | 1:11 |
| Discover | The App Map | 0:33 |
| Discover | Read the Action List | 0:39 |
| InSight | InSight in three minutes | 0:59 |
| Integrations | Integrations | 0:46 |
| Maintain | Review auto-heal repairs | 0:36 |
| Project Panel | Tune how a project runs | 0:46 |
| Quick Start | SmartestQA at a glance | 1:42 |
| Report | Read a pipeline report | 0:42 |
| Schedule | Your first pipeline | 2:16 |
| Schedule | Setup, Before, After and Teardown | 0:47 |
| Schedule | Schedule a nightly run | 0:43 |
| Schedule | Server or agent? | 0:44 |
| Schedule | Run, stop and read history | 0:44 |
| Tasks | The task board | 0:32 |
| Tasks | Report a bug by hand | 0:39 |
Didn’t find your answer?Write to support with your project name and what you see on screen.
info@smartestqa.ai