# Glossary

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

## TestVibe Terms

| Term       | Meaning                                                                                          |
| ---------- | ------------------------------------------------------------------------------------------------ |
| Project    | A TestVibe workspace connected to a GitHub repository and target application.                    |
| Test Suite | The organized tree of groups, features, and tests for a project.                                 |
| Group      | A folder or collection used to organize related tests.                                           |
| Feature    | A Gherkin `.feature` file that describes behavior in user-readable scenarios.                    |
| Scenario   | One example of behavior in a feature file, written as steps such as `Given`, `When`, and `Then`. |
| Test       | A runnable Playwright test or a TestVibe test item in the suite.                                 |
| Generation | The AI-assisted process that creates or updates feature files or Playwright test code.           |
| Run        | A GitHub Actions execution that runs selected tests against a site URL.                          |
| Result     | The pass/fail output and evidence from a completed run.                                          |
| Artifact   | A file produced by a run, such as screenshots, videos, traces, logs, or reports.                 |

## GitHub Terms

| Term         | Meaning                                                                     |
| ------------ | --------------------------------------------------------------------------- |
| GitHub App   | The TestVibe installation that grants repository access.                    |
| Installation | A GitHub App connection to a personal account or organization.              |
| Repository   | The GitHub project where tests, workflows, and settings live.               |
| Workflow     | A GitHub Actions automation file that generation or test runs execute.      |
| Workflow run | One execution of a workflow.                                                |
| Runner       | The machine GitHub uses to execute workflow jobs.                           |
| Secret       | An encrypted value used by workflows, such as API keys or test credentials. |
| Variable     | A plain configuration value used by workflows.                              |

## 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.                 |
| Canceled        | The workflow or 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.                                              |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.testvibe.com/reference/glossary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.