Overview
Discover Test Companion, an AI-powered testing assistant that integrates into your IDE to help you generate test cases, write automation scripts, debug failures, and fix accessibility issues without leaving your editor.
Test Companion is currently in the alpha phase.
Test Companion is an AI-powered testing assistant that operates within your IDE. It generates test cases, writes automation scripts, debugs failures, and fixes accessibility issues for both web and mobile applications, all without requiring you to leave your editor.
You can interact with Test Companion through a chat interface in the IDE sidebar. Simply describe your needs in plain language, and Test Companion handles the details. It reads your requirements, explores your application, writes test code, and diagnoses any failing builds. Everything stays within your editor and connects directly to the BrowserStack ecosystem.
What you can do
Test Companion is designed to assist you throughout the entire testing lifecycle. Following are some of the key tasks you can accomplish:
-
Generate test cases: Create detailed scenarios with steps, expected results, and priority levels from PRDs, specifications, user stories, or by directing the AI to a live URL or mobile app. For mobile apps, upload an
APK,AAB,XAPKorIPAfile and let the AI explore your app on BrowserStack’s real device cloud. -
Write automation scripts: Produce code for any framework, including Playwright, Cypress, WebdriverIO, Selenium, Appium, and more. You can convert existing manual test cases into code or describe a new test from scratch. This works for both web and mobile applications.
-
Debug and fix failing tests: Connect to BrowserStack Test Reporting & Analytics or paste error logs into the chat. The AI will identify the root cause of the problem and suggest code-level fixes.
-
Find and fix accessibility violations: Scan your web application against WCAG standards to identify accessibility issues. The AI can apply automated code remediation directly to your source files.
-
Test mobile apps on real devices: Upload an APK, AAB, or IPA file, and allow the AI to explore your app on BrowserStack’s device cloud. It will generate test cases and automation scripts based on its findings.
-
Validate code changes as a developer: Use the Dev Tester agent, a shift-left tool that understands your local codebase and generates tests specific to what you are currently building—before the code reaches QA.
Choose your path
Test Companion serves different roles at various stages of the testing process. Start with the section that matches your current needs.
I am setting up for the first time
Install the extension, sign in with your BrowserStack account, and configure Test Companion to align with your project standards.
→ Get Started
I am testing a web application
Follow the complete QA workflow, which includes generating test cases, managing them, automating scripts, fixing failures, and remediating accessibility issues. You can also use Dev Testing to validate your code changes before they reach QA.
→ Web Testing
I am testing a mobile application
Connect your iOS or Android app, generate test cases by exploring it on real devices, or from requirement docs like PRDs and Jira links, and create automation scripts—all from your IDE.
→ Mobile Testing
How it works
Test Companion utilizes specialized AI agents, each designed for a specific testing task. You select the appropriate agent from the dropdown at the bottom of the chat panel, provide context (a file, a URL, a prompt, or workspace references with @), and the agent will take action.
Core Agents
-
Tester: A general-purpose agent that manages the entire QA testing lifecycle. It is suitable for broad, end-to-end tasks and is a good default option if you are unsure which specialized agent to choose.
-
Dev Tester: A developer-focused agent that reads your local codebase, comprehends your current changes, and tests your code changes. It is specifically designed for use before the code enters the traditional QA cycle.
Specialized Agents
You do not need to memorize which agent to use. Each guide in this documentation indicates which agent to select for specific tasks.
| Agent | What it does |
|---|---|
| Test Case Generator | Reads requirement documents (PRDs, specifications, user stories) and creates structured test cases. |
| Exploratory Tester | Opens a browser or mobile device, navigates through your application, and discovers testable scenarios. |
| UI Test Generator | Converts manual test cases into executable browser automation scripts. |
| API Test Generator | Creates API test suites from endpoint URLs, OpenAPI specifications, or descriptions. |
| Test Fixer | Analyzes test failures from CI builds or local runs and suggests code-level fixes. |
| A11y Fixer | Scans web applications for WCAG violations and applies automated code remediation. |
BrowserStack platform integration
Test Companion integrates with the broader BrowserStack ecosystem, ensuring your work in the IDE remains synchronized with your team’s tools.
-
Test Management: Sync test cases you generate or edit in your IDE directly to BrowserStack Test Management. Your tests are versioned, organized, and accessible to your entire team. You can also fetch existing test cases from Zephyr Scale and Xray to automate them within your IDE.
-
Test Reporting & Analytics: Pull build results and failure data into your IDE. The Test Fixer agent reads failures from TRA, diagnoses the root cause, and suggests fixes without requiring you to leave the editor.
-
App Automate: When testing mobile apps, Test Companion starts real device sessions on BrowserStack’s cloud infrastructure. The AI interacts with your app on actual iOS and Android devices, capturing UI hierarchy and screenshots to generate accurate test code.
-
Automate: Run your generated web automation scripts on BrowserStack’s browser cloud for large-scale cross-browser validation.
Next steps
-
Get started if you have not installed the extension yet.
-
Web testing to begin testing a web application.
-
Mobile testing to start testing a mobile app.
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!