Overview and quick start

AIQ New Functionality · WebDesigner – New Functionality

SETUP AND OPERATIONS GUIDE   Reviewed 16 Nov 2026

Run DesignerScript against BrowserStack cloud desktop browsers and real mobile browsers from WebDesigner or AIQ. This guide takes you from obtaining account details to configuring profiles, running a test, finding its evidence, and diagnosing failures.

Scope: this is the new WebDesigner/DSServer integration for testing websites, including websites in mobile browsers. Native mobile applications and the older Mobile Designer/App Automate workflow have separate setup. The behavior below requires matching BrowserStack-enabled AIQ, frontend, shared-library and DSServer builds.

Current acceptance boundary: selected desktop and mobile playback flows have passed. Accessibility scans and final report logging have been verified on Windows 11 Chrome. Distributed AIQ scenarios, the newest starter targets, and mobile accessibility remain unverified. The Android full-page snapshot defect, where the top screen repeated down the image, was fixed and verified on a Pixel 9 / Android 15 on 16 Nov 2026. See the verification matrix before planning coverage.

Quick start

  1. Sign in to BrowserStack with the account your team will use. Confirm Automate entitlement, the required desktop/mobile targets, and available parallel capacity.

  2. Get the account’s Username and Access Key from Account & Profile. Keep the access key private.

  3. In AIQ, open Admin Options → Services → BrowserStack as an administrator or owner.

  4. Enter the credentials, keep the Local base path at ./browserstack-local, and begin with one concurrent session per node.

  5. Load/refresh the catalog, enable a desktop Chrome profile, choose a stable project name, and decide whether this account should run accessibility scans.

  6. Enable the integration and click Save settings. For WebDesigner on your own workstation, start it and click Apply to My Local Webdesigner.

  7. Refresh the browser selector, choose BrowserStack-Chrome-Latest-Windows11, run a short normal-mode test, and stop it.

  8. Confirm the session has ended in BrowserStack Automate and look for BrowserStack remote stop acknowledged in the DS operational log.

A successful first run proves: the profile is available, the cloud browser reaches the application, DesignerScript actions execute, and the cloud session closes. If accessibility is enabled, also confirm scans were saved and inspect the final Accessibility report.

How the integration works

Stage What happens What you control
Configure AIQ stores the account and enabled profiles. Each receiving DSServer saves its configuration to its own active global.json. Credentials, enabled profiles, per-node concurrency, project name and accessibility settings.
Start DSServer checks availability and capacity, creates a session-owned proxy route and starts BrowserStack Local, then allocates one cloud browser session. Choose a saved BrowserStack profile. Normal mode is required.
Run Cloud web traffic passes through BrowserStack Local and the owning DS proxy. Existing DesignerScript injection and playback drive the application. Use the script’s normal navigation, accessors, assertions and waits within the target’s supported scope.
Finish DSServer finalizes accessibility when enabled, deletes the cloud session, stops its Local tunnel and releases the node slot. Final accessibility counts are fetched in the background. Stop interactive sessions; check cleanup and the final report.

Traffic path: BrowserStack browser → BrowserStack Local tunnel → session-owned DSServer proxy → application under test. The execution machine must be able to reach the application. Local is part of this integration even for publicly reachable websites.

Each run receives a unique name, AIQ-<yyyyMMddHHmmss>-<DS session>-<32-character id>, used for its BrowserStack session and Local tunnel. The timestamp uses the execution node's local time. The build name follows the Build name setting: the run's unique name (default), one build per day AIQ-YYYY-MM-DD, or always AIQ-Executions. An optional Build name suffix is added to any of them after a dash, for example AIQ-2026-11-17-Avantor. Retain the full unique session name when correlating evidence; in a shared build, find a run by its session name.

Target Control connection Practical consequence
Desktop Chrome / Edge CDP when available; otherwise WebDriver. Native protocol features depend on attachment succeeding.
Desktop Firefox BiDi when available; otherwise WebDriver. Do not infer full local-Firefox feature parity.
Desktop Safari WebDriver. Uses HTTP browser-message transport and provider network logging for HTTPS trust.
Android Chrome WebDriver through Appium. No attached CDP session; full-page snapshots are stitched, which takes longer than on desktop Chrome.
iPhone / iPad Safari WebDriver through Appium. Uses buffered WebSocket browser messages and provider network logging for HTTPS trust.

Revision #1
Created 2026-11-17 17:43:57 UTC by Admin
Updated 2026-11-17 17:43:57 UTC by Admin