Glossary
Terms used in Reelspect and in this manual, in alphabetical order.
| Term | Definition |
|---|---|
| Active | Test case status for a test case in use; also a test plan status. See Library. |
| Admin | Organization role that manages members, projects and integrations; Manager in every project unless given another role. See Roles. |
| Agent | The AI tester that carries out a test case from screenshots. See Writing test cases. |
| Archived | Test plan status for a plan kept for reference only. See Test plans. |
| Attachment | A file on a test case, plan or run; the agent reads text files only. See Attachments. |
| Blocked | Verdict: the test could not be carried out; says nothing about the product. See Verdicts. |
| Cancelled | A run, test or session stopped before it finished. |
| Chat | Session viewer tab for questions about one session. See Session viewer. |
| Collection | A nestable folder for test cases in the Library or the Sandbox. See Library. |
| Completed | Run status: finished with no Failed or Error test; also a test plan status. |
| Decommissioned | Test case status: hidden from the Library and excluded from new runs; can be reactivated. |
| Deprecated | Test case status: outdated but kept; not added to runs. |
| Description | Notes for people on a test case, plan or run; never sent to the agent. |
| Device Bridge | Connects your own iOS simulators and physical devices to Reelspect. See Device Bridge. |
| Device preset | The device a test runs on: a desktop size, a simulator or a physical device. See Devices. |
| Draft | Starting status of a new test case, test plan or run. |
| Error | Verdict when a session ended without a report; run status when a system problem stopped the run. |
| Execution | One attempt at running a test case. See Execution history. |
| Execution strategy | Parallel, Sequential or Single Session. See Execution strategies. |
| Failed | Verdict: the product did not do what the test expected. A run with any Failed or Error test is Failed. |
| Knowledge | What Reelspect has learned from earlier sessions, and the page to ask about it. See Knowledge. |
| Library | The project’s shared test cases. See Library. |
| Manager | Project role that can do everything in a project, including statuses, settings and members. |
| Member | Organization role without admin rights; project access comes from project roles. |
| N/A | Test status set by hand when a test does not apply. |
| Observer | Monitor that warns when a session loops or is stuck (Low to Critical). See Session viewer. |
| On failure | Multi-round option: Continue all rounds (default) or Stop on first failure. See Rounds. |
| Organization | Your company’s space, holding members, projects, devices and integrations. |
| Override | Changing a test’s verdict by hand, with a required reason. See Overriding a status. |
| Parallel | Execution strategy: each test case in its own session, all at the same time. |
| Passed | Verdict: the product did what the test expected. |
| Phase | A named section of a session’s timeline, from the automatic session report. |
| Project | A body of testing work with its own Library, Sandbox, runs and members. See Project settings. |
| Promote | Copy a Sandbox test case into the Library. See Promote to Library. |
| Public project | A project every organization member can open as a Viewer. See Roles. |
| Queued | Waiting for capacity; starts automatically when capacity frees up. |
| Requested Output | Structured data the instructions asked for, downloadable as CSV or JSON. See Requested output. |
| Resource Monitor | The header ring that shows running and queued work. See Getting started. |
| Retest | Test status set by hand to mark a test for running again. |
| Round | One pass over all test cases of a run; 1 to 100 per launch. See Rounds. |
| Run | Test cases with a device, a source URL, instructions and an execution strategy. See Runs. |
| Run item | One test case inside a run, with its verdict and executions, in the run’s Tests list. |
| Running | A run, test or session in progress. |
| Sandbox | Your private space in a project for drafting and launching test cases. See Sandbox. |
| Schedule | Launches a run automatically, from every 15 minutes to monthly. See Schedules. |
| Scratchpad | The agent’s own notes during a session, shown in the Session viewer. |
| Send to Sandbox | Copy a Library test case into your Sandbox to try changes. |
| Sequential | Execution strategy: each test case in its own session, one after another. |
| Session | One execution of a test case by the agent, made of turns, with a replayable recording. |
| Session viewer | Shows a session live or as a replay. See Session viewer. |
| Single Session | Execution strategy: all test cases one after another in one shared browser session. |
| Skipped | Test not run, for example no device set or the device is not available to the launcher; can be set by hand. |
| Source | Where the agent starts: a URL, or URLs in the instructions or a text attachment. |
| Tag | A coloured label for test cases, runs and plans. See Project settings. |
| Test case | A titled set of plain-language instructions for the agent, with optional attachments. |
| Test Instructions (Prompt) | The instructions field on test cases, plans and runs; the only text the agent receives. See What the agent receives. |
| Test plan | A group of runs with shared instructions and attachments. See Test plans. |
| Tester | Project role that creates and edits test cases, plans, runs and schedules, and launches runs. |
| Trigger | Run detail row that always reads Manual; check Launched by to see if a schedule launched it. |
| Turn | One step of a session: look at a screenshot, decide, act. Up to 500 per session. |
| Untested | Test status before a test has run. |
| Verdict | Passed, Failed, Blocked or Error. See Verdicts. |
| Version | Each Library edit creates a new version (v1, v2); each execution records the version it ran. |
| Viewer | Project role that sees everything and uses their own Sandbox, Knowledge and chat, but cannot change shared work. |