QE Blocks Tests V2 MCP Guide

Playwright E2E tests with mandatory @qe/blocks integration, including transformation of existing tests and BLAW-specific helpers.

URLs and JSON

Mount: /mcp/v2/blocks. Config key: qe_blocks_tests_v2. Legacy V1 mounts under /mcp/qe_blocks_tests (including older BBVPN V1 URLs) are deprecated — use V2 only.

{
  "mcpServers": {
    "qe_blocks_tests_v2": {
      "url": "https://qe-mcp.bindg.com/mcp/v2/blocks",
      "transport": "http"
    }
  }
}

{
  "servers": {
    "qe_blocks_tests_v2": {
      "url": "https://qe-mcp.bindg.com/mcp/v2/blocks",
      "type": "http"
    }
  },
  "inputs": []
}

Tools

Add to Cursor

1. Open Cursor and go to Settings.
2. Find Tools & MCP and choose New MCP Server.
3. Paste the Cursor JSON above (or a single entry).
4. Save.
5. Look at Installed MCP Servers to confirm the server is connected.

Add to VS Code

1. Open VS Code, then the Command Palette.
2. Search for MCP: Add Server and select HTTP.
3. Enter the URL https://qe-mcp.bindg.com/mcp/v2/blocks.
4. Provide an alias name such as qe_blocks_tests_v2.
5. Save globally or to the workspace, then start the server.

@qe/blocks package setup

Before using this MCP, ensure @qe/blocks is installed:

npm install @qe/blocks

The package is available from Artifactory. Add the registry to .npmrc:

registry=https://artifactory.bna.com/artifactory/api/npm/npm-virtual/

Blocks fixtures usage

All generated UI tests use Blocks fixtures with a bl parameter:

import { test, expect } from '@qe/blocks/new-fixtures';

test('example', async ({ bl }) => {
  await bl.goto('/page');
  await bl.click('[data-testid="button"]');
  await bl.verifyElements('[data-testid="element"]');
});

Mandatory transformation rules

The MCP automatically transforms raw Playwright patterns to Blocks equivalents:

BLAW-specific Blocks functions

For Bloomberg Law products, the MCP can use specialized Blocks namespaces:

Generation workflow

1. Repository analysis

• Identify framework, routing, state management, and build tooling.
• Check for @qe/blocks in package.json (required).
• Verify Artifactory registry configuration in .npmrc.
• Find existing Playwright config, page objects, fixtures, utilities.
• Detect Blocks usage patterns (fixtures vs class-based).
• Identify testable user flows and core features.

2. Test architecture proposal

• If tests exist: integrate with current structure and conventions.
• If none: propose feature-based layout with POM/Screenplay, fixtures, parallelization, retries.
• Recommend Blocks fixtures (@qe/blocks/new-fixtures) for all new tests.

3. Test generation (non-destructive)

• Create new test files only.
• Never overwrite config, page objects, fixtures, utilities, or existing tests.
• Use Blocks fixtures and transform all Playwright patterns.
• Use semantic selectors (prefer data-testid).
• Follow AAA with clear Arrange / Act / Assert separation.
• Prefer stable waits over waitForTimeout.
• Propose data-testid additions when selectors are missing.
• Include { bl } parameter in every test function.

Key principles

The MCP behaves like a senior Playwright architect. Key principles, condensed:

Example prompts

Codegen integration with Blocks

The assistant should transform:

• import { test, expect } from '@playwright/test' → import { test, expect } from '@qe/blocks/new-fixtures'
• page.goto() → bl.goto()
• page.locator().click() → bl.click()
• page.locator().fill() → bl.inputText()
• expect().toBeVisible() → bl.verifyElements()
• Add { bl } parameter to all test functions.
• Apply AAA, semantic selectors, and save to tests/[feature-name]/.

BBVPN proxy configuration

{
  "http.noProxy": [
    "qe-mcp.bindg.com"
  ]
}

Validate the connection