Feature settings
Set Test Companion test case generation defaults and toggle optional features such as checkpoints, notifications, and GitHub integration.
Feature settings has two parts. The Test Cases controls set the template, type, priority, and language that generated test cases use. The checkboxes below them turn optional capabilities on or off, such as checkpoints, desktop notifications, or Electron app testing support. You can enable or disable each one independently.
How to open settings
To open the feature settings:
Click the Settings gear icon at the top-right corner of the Test Companion panel.

Select the Feature Settings tab.

Set your test case generation defaults, then click Save.
Test case generation defaults
The Test Cases controls set the defaults Test Companion uses when it generates test cases. They apply to every test case generated after you save. You can override them for one run by saying so in the chat, for example “generate BDD test cases in Spanish”.
Template
The Template dropdown sets the test case format, matching the formats on the Generate screen in BrowserStack Test Management. Your project’s own templates are listed after the built-in ones.
| Setting | Details |
|---|---|
| Field type | Dropdown |
| Default value | Steps |
| Options | Steps, BDD, Text, Custom, followed by your project’s own templates |
| What it does | Sets the format Test Companion uses when it writes test cases. |
- Steps produces step-by-step test cases. Each case lists explicit actions and the expected result for each step. Choose it when you read test cases as a numbered sequence, or when you import the output into a test management tool that expects discrete steps.
-
BDD produces test cases as Gherkin-style
FeatureandScenarioblocks with Given, When, and Then steps. Choose it when your automation framework consumes.featurefiles or you write acceptance criteria in Given-When-Then form. - Text produces each test case as plain text, with the description, preconditions, steps, and expected results written as prose. It matches the Text template in Test Management. Choose it for short, unstructured scenarios.
- Custom uses one of your Test Management project’s own templates. The project templates appear in the dropdown after the built-in ones when a Test Management project is connected.
Under the template, select Shared steps to reuse the connected project’s shared steps and let Test Companion propose new ones. Select Include datasets to generate test data alongside the test cases. The Include datasets checkbox appears only on accounts with datasets enabled, and you cannot select it together with Shared steps. Shared steps, datasets, and project templates apply to BrowserStack Test Management only.
Type and priority
Under Type, select the test case types Test Companion generates: Functional, UI/UX, Security, Performance, Compatibility, and Accessibility. At least one type stays selected.
Under Priority, select the priorities Test Companion assigns: Critical, High, Medium, and Low.
Language
The Language dropdown sets the language Test Companion writes generated test cases in. It is separate from the Preferred Language in General settings, which controls the chat.
Feature toggles
The checkboxes below the test case controls turn individual capabilities on or off.

Enable checkpoints
When checkpoints are enabled, Test Companion automatically saves a checkpoint of your workspace files at important moments while it works on a task. For example, before modifying a file or before running a command that could change your project state. If the AI makes a change you are unhappy with, you can revert to an earlier checkpoint instead of manually undoing the changes.
| Setting | Details |
|---|---|
| Field type | Checkbox |
| Default value | Enabled (checked) |
| What it does | Saves snapshots of your workspace at key points during a task, so you can roll back if something goes wrong. |
Under the hood, checkpoints use Git to track workspace state. The extension creates lightweight commits behind the scenes to mark each checkpoint.
When to enable checkpoints
Checkpoints are valuable in most situations and are enabled by default. They are especially useful when:
- You are letting Test Companion work autonomously in Agent interaction mode
- The AI is making changes across multiple files at once
- You are experimenting with different approaches and want to easily backtrack
When to disable checkpoints
There are specific cases where you may want to turn checkpoints off:
- Very large workspaces: If your repository is exceptionally large (for example, a monorepo with tens of thousands of files), the Git operations behind checkpoints can slow down. If you notice sluggish performance during tasks, try disabling checkpoints.
- Non-Git projects: If your workspace is not a Git repository and you do not want one to be initialized, disable this feature.
Show agent edits in editor
When this setting is on, Test Companion opens a diff view for each file it edits. You can watch changes as they happen. It is on by default. Turn it off to keep your editor where you left it while the agent works. Edits still appear in the chat, and the File changes panel lets you review, keep, or undo them.
Enable notifications
This is particularly useful when you start a task and then switch to another window or application while the AI works. Instead of periodically checking back, you receive a notification that brings you back to your IDE at exactly the right moment.
| Setting | Details |
|---|---|
| Field type | Checkbox |
| Default value | Disabled (unchecked) |
| What it does | Sends you a system notification when Test Companion needs your approval to continue, or when a task is completed. |
Example use case
You ask Test Companion to generate a full test suite for your user registration module. You switch to your browser to review the application’s UI while the AI works. A few minutes later, you receive a desktop notification that reads Test Companion requires approval to proceed. You switch back to your IDE. Test Companion wants to create a new file. You approve, and it continues.
When to enable notifications
- When you multitask and frequently switch away from your IDE while the AI is working
- When using Plan mode, where Test Companion waits for you to approve the plan
- For long-running tasks where you want to be alerted upon completion
Sound notifications for background activity
When this setting is on, Test Companion plays a sound when a process needs your attention. The sound plays even when you are working in another window. It is off by default. The checkbox appears only on accounts with background sessions enabled.
Enable GitHub integration
When this setting is on, Test Companion offers to open a GitHub pull request from the chat. The offer appears after it writes or fixes test files. It runs git and gh on your machine to do so. It is on by default. Turn it off to hide the Create PR card.
Enable Electron
Electron testing is a beta feature. Its features and availability might change in future releases. In Feature Settings, the Enable Electron checkbox shows a Limited badge.
Electron is a framework used to build cross-platform desktop applications with web technologies (HTML, CSS, JavaScript). Many popular applications, such as VS Code, Slack, and Figma, are built on Electron.
| Setting | Details |
|---|---|
| Field type | Checkbox |
| Default value | Disabled (unchecked) |
| What it does | Enables testing of Electron-based desktop applications, including VS Code extensions and custom desktop apps. |
When this setting is enabled, Test Companion can understand and interact with Electron application structures, including:
- Testing VS Code extensions within the Extension Host
- Interacting with custom Electron app windows
- Analyzing Electron-specific APIs and IPC (inter-process communication) patterns
- Generating tests that account for Electron’s main process and renderer process architecture
When to enable Electron
- You are developing a VS Code extension and want to generate or debug tests for it
- You are building a desktop application using Electron and need testing assistance
- Your test automation needs to interact with Electron application windows
When to leave Electron disabled
If your testing work is limited to web applications and mobile apps (the most common use case), leave this disabled. Keeping it off avoids any unnecessary overhead or unintended Electron-related suggestions from the AI.
Enable repo onboarding
When this setting is on, Test Companion learns your repository’s test setup in the background when you open it. Later tasks then start with accurate project context. It is on by default and consumes no AI credits.
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!