Skip to main content
Free plan, no cardStart free
Workflow automation 8 min read Updated

QA Testing beyond the canvas: files, data, bots, queues and the exception desk

The workflow canvas is one tab of QA Testing. Around it: Test Files, the per-user library every plan has for the files your tests upload and download; Data Add, folders of test data a workflow reads; Document Update, which runs a workflow once per row of a file; Run as Bot, which compiles a recording into self-healing keyword steps; Queues, the work your bots go through one item at a time; Test Result, the execution history with screenshots and node results; Exceptions & Ledger, where a stopped item waits for a person; and Assets & Connections, the named values, logins and outside systems a bot works with. The tabs beyond Test Files are on the Team plan.

About this guide

Written for
QA leads and test managers · SDETs and automation engineers · Engineering managers

Which plan

QA Testing (workflow build, Search & Collect, the data store, document update and test results) is part of the Team plan; on another plan the page says so and links the plans, or you buy the QA workflows tool on the pricing page. Test Files is different: every plan has it, with an allowance per user of 25 MiB on Free and Solo Pro, 50 MiB on Team and 100 MiB on Enterprise, up to 500 files and 45 MiB per file, across 69 file types. A program, a macro-enabled Office file, a certificate or a key is refused.

Test Files

Drag files in or choose them; Excel, CSV, JSON, PDF, Word and images are parsed on upload and the parsed data can be viewed. A file with the same name as one you already have asks whether to replace it, keep both or not upload. Every file is checked: a virus scan, and a check that the bytes match the name, so a file that contradicts its extension is marked suspect and withheld from runs. Deleted files go to the trash, which you empty to free space (that cannot be undone), and "Download all my files" gives you the whole library. A file the recorder picked for a page during a recording lands here too, and an upload step in a test folder or a workflow names a file from here.

Data folders and Document Update

Data Add stores test data in folders for workflows to read: pasted, imported from an uploaded file or from a run, or saved by a run. Document Update runs a chosen workflow once for every row of an uploaded file or of a data-store entry, which is how a hundred records are processed by one workflow without a loop node.

Run as Bot, and the queues

Run as Bot compiles a recorded session into keyword steps and runs them on the bot engine, with retries, selector self-healing and a concurrency governor. Password fields are filled from data at run time and never stored in the bot.

A queue holds the work your bots go through one item at a time: an invoice, an order, an e-mail. Robots claim the next item, work it and record the outcome; a failed item is retried by the queue's rules (an application error is retried with backoff, a business exception is never retried), and you can retry, delete or reprioritise items yourself. Archiving a queue stops new items and new claims, lets the items in progress finish, and cannot be undone.

Results, exceptions and the run ledger

Test Result is the execution history, filtered by status, with each run's node results: an API step with its extracted variables, response headers and body; generated data; an e-mail trigger with its message id; the fields a data edit changed; a screenshot where there is one. Text written by a model carries the badge "AI · unverified", because model-authored text is never a confirmed finding.

Exceptions & Run Ledger is the desk for keyword items that stopped and need a person: retry them, hold them, assign them, or dismiss them with a reason; the failure-pattern and item-health views show which items are flaky or quarantined. Any run opens by its id, with its rules verdict, its advisory analysis, every item's row and its signed manifest.

Assets & Connections

Assets are named values and logins a step reads as `{{name}}`; connections are the APIs, file servers and mailboxes a bot works with. Both are typed once, can differ by environment, and their secrets are never shown again after you save them.

Questions people ask about this

Are my Test Files shared with my team?
A file is yours unless you share it with the team; the allowance is counted per user. A run uses the runner's files and the author's team-shared files, never another person's private file.
What does the exception desk retry on its own?
Application errors, with backoff, by the queue's rules. A business exception, where the data itself is wrong, waits for a person and is never retried automatically.
Where do the files a workflow downloads go?
Into the run's own folder, after the same check every download gets, and a later step of the same run can use them. They do not land in your library unless you keep them there.

Source: /documentation/qa-testing-files-bots-queues, updated 2026-11-16. Answers are checked against the shipped product on that date.

Found something out of date? The people who build the module answer the contact form on the home page, and corrections to this guide are dated above. Tell us.

This guide is about QA workflows, the keyword engine and the bot console. Twenty tools, including ours, are compared by job.

Try it against your own app.

Record one flow and get four kinds of evidence back. Judge the results yourself.

  • Free plan, no card
  • 14-day Solo Pro trial
  • Demo replies within one business day
  • Data hosted in India