Glossary
Key terms used throughout BlinqIO AI Test Engineer documentation.
A
AI Chat
A step creation mode where you describe the desired action in natural language and AI generates the Gherkin step name and Playwright code.
AI Enhance
A feature that generates dynamic expressions (Faker.js, JavaScript, date functions) for test parameters instead of static values.
AI Record
A step creation mode where you interact with the browser and AI captures your actions as recorded steps with generated Playwright code.
Assert
A step creation mode for adding verification checks (text found, element property, page title, page snapshot, text relation).
B
Browser Preview
The right panel in the AI Test Engineer showing a live view of the target application. Used for recording, running, and visual verification.
Bulk Actions
The ability to select multiple tests and perform batch operations (run or delete) from the AI Tests page.
C
Code Viewer
The expandable section on each step card showing the generated Playwright TypeScript code with syntax highlighting.
Custom
A step creation mode for specialized actions: context clicks, value extraction, fixed sleep, and fluent sleep.
D
Data Panel
The collapsible bottom section of the AI Test Engineer showing extracted parameters (Step Inputs tab) and project-level data (Project Data tab).
E
Environment
A target URL where tests run (e.g., Production, Staging, QA). Each project can have multiple environments. Also called "Test URL."
Examples Table
The Gherkin concept of a data table that provides different parameter values for a Scenario Outline. Visible in the Step Inputs tab.
F
Feature
A collection of related tests within a folder. Maps to a Gherkin Feature file.
Folder
An organizational container in the test tree. Can contain subfolders and features.
G
Gherkin
An industry-standard, human-readable language for describing test scenarios using Given/When/Then syntax. BlinqIO uses Gherkin Scenario Outline format.
Given / When / Then
The three primary Gherkin keywords. Given sets up preconditions, When describes the action, Then defines the expected outcome. And / But continue the previous keyword's context.
L
Lock Indicator
A visual marker on a test card showing that another team member is currently editing the test. Locked tests cannot be modified.
O
Onboarding Wizard
A guided tour that appears on first visit, introducing the core BlinqIO workflow. Can be replayed via the help button.
P
Parameter
A dynamic value in a step name, written as <paramName>. Parameters are extracted into the Test Data panel for editing and can be enhanced with AI-generated expressions.
Playwright
An open-source browser automation library by Microsoft. BlinqIO generates Playwright TypeScript code for each test step.
Project
The top-level workspace in BlinqIO. Each project owns its own test tree (folders and features) and environments.
R
Reuse
A step creation mode where you select an existing step from your step library to reuse in the current test.
Run All
The command to execute all implemented steps in sequence, validating each one against the browser.
S
Scenario Outline
A Gherkin construct that defines a test template with parameters, paired with an Examples table for data-driven execution.
Step
One action or verification within a test. Each step is in Given/When/Then format and is backed by generated Playwright code.
Step Card
The UI component representing a single step in the AI Test Engineer. Can be collapsed (compact) or expanded (full editing UI).
T
Test
A single end-to-end automation scenario, made up of sequential steps. Maps to a Gherkin Scenario Outline.
Test Card
A summary card on the AI Tests page showing a test's name, status, tags, step count, and timestamps.
Test Tree
The hierarchical structure of folders, features, and tests within a project.
Toast Notification
A temporary message card that slides in from the top of the left panel, providing feedback about actions (success, warning, info, error).