# Glossary

URL: https://docs.testvibe.com/reference/glossary

Use this glossary when TestVibe uses a term you want to confirm.

## TestVibe Terms

| Term | Meaning | Artifact | A file produced by a run, such as screenshots, videos, traces, logs, or reports. | Automation | A trigger that starts runs on a cron schedule or an external event, with its own site URL, groups, and configurations. | Cloud test session | The hardware-isolated sandbox allocated for each run. Prepared automatically — no infrastructure to install. | Credits | TestVibe's usage unit. AI tokens and run session time are metered in credits; see Settings → Billing and Settings → Credit Usage. | Feature | A [Gherkin](https://cucumber.io/docs/gherkin/)`.feature` file that describes behavior in user-readable scenarios. | Generation | The AI cloud agent that creates or updates feature files or Playwright test code. Metered in credits. | Group | A folder or collection used to organize related tests. | Journey | A user flow through your app, described by a feature and proven by its generated test. Load tests replay journeys in parallel. | Learned App Fact | Selector-free application behavior TestVibe's agents discover automatically while driving your app — control quirks, timing, DOM shape. Captured as tests generate and expire when the app changes. Reviewable (read-only aside from delete) in Settings → Notes. | Load test | A k6-based run that replays journeys under a load profile (virtual users, duration, ramp-up), dispatched to a cloud load fleet. | Member | A person who belongs to a workspace, with a role of Owner, Admin, Member, or Viewer. Managed in Settings → Members. | Note | Durable instructions you or the assistant write about your app — login quirks, navigation structure, domain vocabulary — injected into every generation. Editable in Settings → Notes. | Plugin | Packaged steps you can call from Gherkin after installing them from the Plugins section. | Project | An application under test, created with a name and the site URL(s) to test. All project content lives in TestVibe's cloud. | Run | One execution of selected tests against a site URL inside a cloud test session. | Scenario | One example of behavior in a feature file, written as steps such as `Given` , `When` , and `Then` . | Secret | An encrypted, write-only value in Settings → Variables & Secrets, referenced from Gherkin as `{{secret:NAME}}` . | Test | A runnable [Playwright](https://playwright.dev/) test or a TestVibe test item in the suite. | Test Suite | The organized tree of groups, features, and tests for a project. | Tunnel device | A machine inside your network running the `tvtunnel` agent so cloud test sessions can reach private apps. Managed in Settings → Tunnels. | Variable | A plain configuration value in Settings → Variables & Secrets, referenced from Gherkin as `{{var:NAME}}` . | Workspace | The container that owns projects, members, billing, credits, and storage. Every user gets a personal workspace and can create or join team workspaces; switch the active one from the header. Billing, plan, and credits belong to the workspace. 

## Result Terms

| Term | Meaning | Passed | The test completed and its assertions matched the expected behavior. | Failed | The test did not meet the expected behavior or hit an execution error. | Skipped | The test was not executed, usually because of configuration or test conditions. | Cancelled | The run was stopped before completion. | Timeout | A step waited too long for an expected condition. | Trace | A Playwright debugging artifact that can show actions, snapshots, network activity, and timing. | Console log | Browser console output captured during a run. | Network details | HTTP requests and responses captured during a run.