Code & Developers
BlinqIO gives you full access to every line of generated source code. There is no vendor lock-in: the test automation code belongs to you, and you can view, edit, debug, and version-control it however you choose.
This section covers the tools and workflows available to developers who want to go beyond the visual interface and work directly with the underlying code.
What you can do
View and edit code online
The built-in online editor lets you open the full .mjs file for any step, inspect the generated logic, and make inline changes without leaving the browser. You can test, discard, or review changes before saving.
Learn more: Viewing and Editing Code
Generate code changes with AI
Describe what you want in plain English and BlinqIO suggests code changes with a side-by-side comparison. Accept the suggestion, discard it, or tweak it further.
Learn more: Viewing and Editing Code
Customize and debug locally
Download the project, open it in VS Code, add breakpoints, install npm packages, and run tests from the debug terminal. The code lives in standard JavaScript files you can modify freely.
Learn more: Customizing and Debugging Code
Store your project in Git
Connect a private Git repository for automatic bidirectional sync. Work with branches, open pull requests in your provider, and keep your test code under version control alongside the rest of your codebase.
Project structure at a glance
Every BlinqIO project follows this layout:
| Path | Purpose |
|---|---|
environments/ | JSON files for each environment (URLs, variables) |
features/ | .mjs step definitions and Gherkin feature files |
node_modules/ | Node.js dependencies |
logs/ | Logs from previous test runs |
reports/ | Metadata and screenshots for test reports |
runs/ | Metadata for previous test runs |
ai_config.json | Project-level AI settings (popup handlers, network idle) |
package.json | Node.js dependency manifest |
Test hooks
BlinqIO uses CucumberJS hooks to let you run custom code at specific points during execution:
| Hook | When it runs | Scope |
|---|---|---|
Before | Before each scenario | Scenario-level |
After | After each scenario | Scenario-level |
BeforeAll | Once before the entire suite | Suite-level |
AfterAll | Once after the entire suite | Suite-level |
Place hooks in any .mjs file inside the step-definitions folder.