BlinqIO Documentation

Troubleshooting & FAQ ​

Common issues and frequently asked questions when using BlinqIO AI Test Engineer.

Common issues ​

AI step generation fails or produces unexpected results ​

Symptoms: The AI generates code that doesn't match your instruction, or the processing phase times out.

Solutions:

  • Be more specific in your instruction. Instead of "login," try "Enter 'admin' in the username field and 'pass123' in the password field, then click Sign In."
  • Break complex instructions into simpler steps. AI works better with focused, single-action instructions.
  • Upload reference documents (PDF, DOC) via the paperclip button to give the AI more context.
  • Check that your target URL is accessible and the page has loaded correctly.

Steps pass individually but fail when run together ​

Symptoms: A step that passed in isolation fails when run as part of a full test sequence.

Solutions:

  • Check for timing issues: the previous step may not have fully completed before the next starts. Consider adding a fluent wait step.
  • Verify preconditions: each step may depend on the state left by previous steps.
  • Check for dynamic content: page elements may change between runs.

Environment switching resets my step statuses ​

This is expected behavior. When you switch environments, all step statuses revert to "Ready" because a step that passed on one environment may behave differently on another. Re-run your steps to validate them in the new environment.

Test name suggestion is not appearing ​

Symptoms: When saving, the AI name suggestion doesn't appear or takes too long.

Solutions:

  • Wait a moment: the AI suggestion loads asynchronously.
  • Type your own name while waiting: the suggestion field is editable.
  • Check your network connection: name generation requires an API call.

I accidentally closed the onboarding wizard ​

Click the help button (?) in the top bar to restart the onboarding wizard at any time.

Frequently asked questions ​

Can I edit the generated Playwright code directly? ​

You can view the generated code using the code viewer toggle on each step. Direct code editing in the browser editor is not currently supported: use AI Chat to regenerate the step with a modified instruction, or export the code to edit in VS Code.

How do I change the target URL for my tests? ​

Click the environment pill in the header, then either select a different environment or click "Manage URLs" to add, edit, or remove environments. See Projects & Environments for details.

Can I run tests in parallel? ​

Parallel execution is available when running tests from the AI Tests page via the BlinqIO Cloud. In the AI Test Engineer, steps run sequentially by design since they build on each other.

What happens to my test data when I switch projects? ​

Each project maintains its own independent test tree, environments, and test data. Switching projects loads the new project's data and clears the previous project's context.

How do I share tests with my team? ​

Tests are shared within a project. Invite team members to your project, and they'll see the same test tree. When a team member is editing a test, it shows a lock indicator to prevent conflicts.

Does BlinqIO support API testing? ​

Yes. You can add API steps to call REST endpoints, configure request parameters, add response checks, and chain API calls. See the Advanced Usage section for details.

What browsers does BlinqIO support for test execution? ​

BlinqIO generates Playwright code, which supports Chromium, Firefox, and WebKit. The browser preview uses Chromium by default.

Can I integrate BlinqIO with my CI/CD pipeline? ​

Yes. BlinqIO tests can be exported as standard Playwright test files and executed in any CI/CD pipeline that supports Node.js. See the Advanced Usage section for CLI execution options.