Testplane Blog

Test run selectivity

Wed, 03 Dec 2025 14:00:00 GMT

Testplane now supports test run selectivity — the ability to automatically run only those tests whose dependency files have changed.

Selectivity allows you to significantly speed up the testing process by running only relevant tests instead of the entire suite. Testplane tracks each test’s dependencies on project files — both the test code itself and the code executed in the browser — and, when a file changes, runs only those tests that depend on it.

How to use

Learn more in our guide How to configure selectivity when running tests.

Conclusion

Upgrade to Testplane version 8.36.0 or higher and try selectivity in your projects! If you encounter any issues, feel free to open an issue on GitHub — we’ll be happy to help!

Testplane vs Playwright: Complete Comparison of Test Automation Tools

Mon, 10 Nov 2025 17:00:00 GMT

Both Testplane and Playwright are end-to-end testing solutions, but they have different approaches and capabilities. In this article, we'll conduct a detailed comparison of these tools to help you make the right choice.

Brief Tool Overview

Testplane is a web application test automation tool developed by the Yandex team. It is actively used in both large and small company projects and supports a wide range of browsers and devices.

Playwright is a tool from Microsoft that has quickly gained popularity due to its ease of use and modern approach to automation.

Key Differences

Browser and Mobile Device Support

tip

Testplane supports both desktop browsers and mobile devices

One of Testplane's key advantages is its versatility in working with desktop browsers and mobile devices. Unlike Playwright, which focuses on modern desktop browsers of the latest versions, Testplane provides full support for both old and new browser versions. This is important for companies that work with users using outdated browsers. A complete comparison of the two approaches can be seen in the table below:

Criteria	Testplane	Playwright	Why It Matters
Browser Source	Original binaries from browser vendors	Custom builds	Maximum proximity to real devices
Browser Versions	Any — from legacy to latest	Browser version tied to Playwright version	Simultaneous coverage of users on both new and outdated browsers
Mobile Devices	Android and iOS: browsers + native applications	No	Unified stack for desktop and mobile devices
Remote Grid	Selenium Grid/Selenoid/BrowserStack/SauceLabs (any remote grid)	Officially — paid Microsoft Playwright Testing; Remote grid — through hacks, without guarantees	Scalability and using your own grid
Protocols	CDP; WebDriver (W3C); WebDriver BiDi	Custom proprietary protocol; CDP (Chromium); WebDriver — no	Browser compatibility and integration flexibility

Visual Testing

tip

Testplane offers advanced visual testing capabilities

In the area of visual (screenshot) testing, Testplane demonstrates clear superiority over Playwright. Under the hood, the tool uses its own looks-same library for screenshot comparison, which is faster and more accurate than current competitors:

Waiting for elements to load before taking screenshots to eliminate test instability;
Disabling animations on the page;
Flexible configuration of screenshot testing sensitivity — tolerance, anti-aliasing tolerance, ignoring a fixed number of pixels;
Uses 3 levels of comparison for speed optimization;
Various types of visualization of differences between screenshots for convenient debugging, including highlighting small diffs;
Ignoring elements in screenshots when necessary.

Testplane provides a convenient interface for bulk screenshot acceptance, which speeds up the process of updating reference images. Also, if Storybook is configured in the user's project, Testplane provides automatic generation of screenshot tests, which allows you to quickly cover all project components with visual checks without writing code.

Playwright offers only basic screenshot testing support with limited capabilities and a less convenient interface for working with screenshots. This makes it less suitable for projects where visual testing is important.

Test Report Interface

tip

Testplane has a powerful UI for working with tests in various scenarios

Testplane has a graphical interface that not only shows the results of your test execution but also provides extensive capabilities for working with them.

This report is perfect for both local work and use in CI. It offers a unified interface for performing various tasks:

Running tests directly from the UI;
Debugging with Time Travel (step-by-step test replay);
Test performance analysis;
Updating reference images in screenshot testing;
Merging multiple reports into one;
Reusing results from CI.

It's especially important that Testplane's report can efficiently work with thousands of tests without losing performance. The plugin system allows customizing reports for specific team needs.

You can explore all report capabilities in the UI section of the https://testplane.io website.

AI Integration

tip

Testplane MCP helps AI agents write stable new tests and fix existing ones

Testplane MCP is a tool that allows AI agents to immerse themselves in the context of what's happening in the browser, perform actions, and create or fix tests based on the real state of the page. With Testplane MCP, users can not only create working and stable tests but also quickly fix existing ones. Testplane MCP allows connecting to the browser during your test execution to debug or modify it. This significantly reduces the time spent fixing unstable tests. Additionally, Testplane MCP provides the ability to run the browser in mobile device emulation mode. For example, you can say "Open example.com page using Testplane MCP on iPhone 15" or explicitly specify which User Agent should be used when creating a browser session.

Extensibility and Integrations

tip

Testplane provides more customization capabilities

Testplane's architecture is built with customization and integration needs in mind. The rich event model provides numerous extension points, allowing developers to inject their own logic at any stage of test execution. This is especially important for projects that require integration with internal monitoring, reporting, and quality management systems. Testplane also provides a JS API that allows creating custom runners adapted to specific project needs.

Playwright, despite its popularity, offers fewer extension points and requires independent development of most integrations. This increases the time for implementation and maintenance of the tool in a corporate environment.

Scaling and Performance

tip

Testplane is proven on large projects with millions of tests

Testplane's architecture was initially designed to work with large volumes of tests, ensuring stable operation even with significant growth in test coverage. This is especially important for long-term projects where the number of tests constantly increases. Support for remote browser grids (e.g., BrowserStack, SauceLabs, etc.) allows efficient distribution of test execution across multiple machines, ensuring fast execution even of very large test suites. Testplane also allows scaling runs through sharding, running tests on different machines. As a result, the user will be provided with a unified report with the results of passed tests.

Playwright also has scaling capabilities in the form of out-of-the-box sharding. Scaling through remote grid is provided only as a paid service Microsoft Playwright Testing.

Updates and Stability

Testplane ensures high stability through a thoughtful approach to dependency management. Tool updates are completely decoupled from browser updates, allowing teams to control the migration process and avoid unexpected failures in CI/CD pipelines. Using stable browser versions minimizes screenshot retaking issues, which is especially important for projects with many visual tests. This approach ensures predictable test behavior and reduces testing infrastructure maintenance costs. Teams can plan browser updates independently of the testing tool updates, providing more flexibility in managing technical debt.

Playwright links tool updates with browser updates, which can lead to unexpected changes in test behavior. This creates additional burden on development teams who have to more frequently review and update screenshots, especially in projects with active interface development.

Selection Recommendations

Choose Playwright if:

✅ Testing only in the latest desktop browsers is sufficient
✅ You're confident that support for old browser versions won't be needed
✅ Visual testing is not required

Choose Testplane if:

✅ Visual testing with convenient reporting is important
✅ Future scaling will be required
✅ Customization for specific needs is important
✅ Testing across a wide range of desktop browsers and mobile devices is necessary
✅ Testing of native Android and iOS applications is required

Testplane MCP

Mon, 16 Jun 2025 17:00:00 GMT

We're excited to present Testplane MCP — a project that allows AI agents to be aware of what's happening in the browser, perform actions, and generate tests based on the real state of the page.

What capabilities does Testplane MCP unlock?

Significant improvement in test generation

Imagine you've added new functionality to your application and now want to generate tests for it using an AI agent. Previously, an AI agent could only guess what this page looks like — the selectors would likely be fictional, and the test would require serious edits.

Testplane MCP takes this process to a new level: while writing tests, the AI agent can open the required page in a browser, look at its layout, or perform any actions (such as clicking a button or filling out a form).

As a result, the AI agent can generate tests with full context of what's happening in the browser — including selectors that actually exist on the page.

Browser usage by AI agents

Testplane MCP makes it possible to automate repetitive processes. For example, you can build a workflow to extract information from receipt photos, then use Testplane MCP to access your organization's management panel and fill out report forms with the corresponding information (item names, quantities, prices, etc.).

Installation

Add Testplane MCP server to the configuration of your IDE.

Open Cursor settings (button in the top right corner of the IDE), in the MCP section click on the Add new global MCP server button, add Testplane MCP to the config as in the example below.

{
    "mcpServers": {
        "testplane-mcp": {
            "command": "npx",
            "args": ["@testplane/mcp@latest"]
        }
    }
}

Install the Cline extension.
On the extension tab, you need to go to the "MCP" tab and click "Configure MCP Servers".

Add Testplane MCP to the config as in the example below.

{
    "mcpServers": {
        "testplane-mcp": {
            "command": "npx",
            "args": ["@testplane/mcp@latest"]
        }
    }
}

Open VS Code settings, search for MCP, click on Edit in settings.json, add Testplane MCP to the config as in the example below.

{
    "mcp": {
        "inputs": [],
        "servers": {
            "testplane-mcp": {
                "command": "npx",
                "args": ["@testplane/mcp@latest"]
            }
        }
    }
}

Open settings as shown in the official documentation, add Testplane MCP to the config as in the example below.

{
    "mcpServers": {
        "testplane-mcp": {
            "command": "npx",
            "args": ["@testplane/mcp@latest"]
        }
    }
}

Open settings as shown in the official documentation, add Testplane MCP to the config as in the example below.

{
    "mcpServers": {
        "testplane-mcp": {
            "command": "npx",
            "args": ["@testplane/mcp@latest"]
        }
    }
}

Open settings as shown in the official documentation, add Testplane MCP to the config as in the example below.

{
    "mcpServers": {
        "testplane-mcp": {
            "command": "npx",
            "args": ["@testplane/mcp@latest"]
        }
    }
}

After installation, the AI agent will be able to use Testplane MCP. You can directly mention this in the prompt: "Use testplane mcp to open the page ...".

Usage

Let's consider the case of developing an online bookstore. Imagine we have a new feature — displaying book ratings and we want to generate tests for this feature.

First, let's ask the AI agent to analyze the page and create a testing plan.

The video tag is not supported by your browser. Download the video.

Now let's try to generate tests and run them.

The video tag is not supported by your browser. Download the video.

As we can see, the AI agent generated tests on the first try that pass and contain correct selectors.

You can try this prompt for generating tests using Testplane MCP:

Use testplane mcp to open the page https://ya.ru, perform a search for "cats", and verify that search results are displayed.

Don't write unnecessary comments in tests, except for complex edge cases. Write tests following the project's style guide.

Try to use semantic selectors, for example, by data-testid attributes or element text instead of complex CSS selectors.

Implementation Details

Testplane MCP is not the only implementation that enables AI agent interaction with browsers.

Currently, Testplane MCP provides the following advantages:

Very compact and flexible page snapshots, models don't need to work with screenshots. This significantly saves LLM API token usage.

As an example — the full source code of https://ya.ru takes ~260,000 characters, while a compact snapshot takes only ~9,000.

Snapshot example

Time Travel + Testplane UI Updates

Wed, 21 May 2025 17:00:00 GMT

We're presenting a new Testplane UI tool — Time Travel, now stable! Let's talk about this new functionality and what else has been added to Testplane UI recently.

How to get the latest updates?

You need to install the latest versions of Testplane and html-reporter:

npm i -D testplane@8.29.2 html-reporter@10.18.0

Time Travel

Time Travel is a new Testplane UI tool that allows you to view test runs in real-time, as well as record and play back all the actions that occurred in the browser during the test.

Here's how it looks:

Time Travel records DOM tree snapshots, which helps debug issues related to selectors while saving disk space.

Learn more in our new guide.

Testplane UI News

Fuzzy Test Search

Test search is now more intelligent and understands queries even with typos or in a different keyboard layout. IDE-like search options have been added: regex and case-insensitive.

We've also added a new sorting method — by relevance. It's automatically enabled during search, ensuring the most relevant tests appear at the top.

New Buttons for Managing Interface Elements

We've added buttons to control the visibility of the test tree and player. Now you can hide them when you don't need them and, for example, work with screenshots in full screen.

The interface remembers your preferences, and even after reloading the page, everything will be as you set it up.

Other Improvements

Significantly reworked the merge-reports command — now it works better, more stable, and covers more cases
Testplane UI can now work with reports created in older versions — no need to worry about losing data when upgrading
New API for exporting snapshots in Time Travel
Option to select playback speed in the Time Travel player

Stay tuned for new releases on our blog and in the Release Notes on GitHub, and if you encounter any issues, please visit our GitHub issues — we'll be happy to help!

WebDriver BiDi protocol support

Tue, 06 May 2025 14:00:00 GMT

Support for the WebDriver BiDi protocol (the future unified standard for browser automation) has been added in testplane@8.27.0.

WebDriver BiDi (Bidirectional) is a new cross-browser automation protocol that combines the best features of existing protocols: W3C WebDriver and Chrome DevTools Protocol (CDP) (you can read more about them in our article). Essentially, the new protocol extends the existing W3C WebDriver protocol and adds new cross-browser commands that replace the CDP protocol (which is not cross-browser compatible). Old webdriver commands still work via HTTP, while new commands provide bidirectional communication between the client and the browser via a WebSocket connection.

The new protocol is currently supported by the following browsers: Chrome, Firefox, Edge. Safari support is not available yet. You can follow the supported browsers on this page.

A list of BiDi protocol commands is available on this page.

How to use?

warning

BiDi protocol support in Testplane is available in browsers starting from version: chrome@128 and firefox@129.

To use the BiDi protocol, you need to:

install testplane@8.27.0 or older;
specify the capability webSocketUrl: true in the desiredCapabilities field for the desired browser (it will be set by default in the next major version);
run the tests.

What can be done with the new protocol?

Tracking and intercepting network requests/responses

You can mock a request to testplane.io and return your own response:

it("should mock testplane.io", async ({ browser }) => {
    await browser.networkAddIntercept({ phases: ["beforeRequestSent"] });

    browser.on("network.beforeRequestSent", networkRequest => {
        browser.networkProvideResponse({
            request: networkRequest.request.request,
            body: {
                type: "string",
                value: "hello world",
            },
        });
    });

    await browser.url("https://testplane.io");
});

Your browser does not support the video tag. Download the video.

We will intercept all requests to the testplane.io resource and display a list of all loaded URLs:

it("should log all loaded urls", async ({ browser }) => {
    browser.on("network.responseCompleted", networkResponse =>
        console.log("got response from url:", networkResponse.response.url),
    );

    await browser.url("https://testplane.io");
});

Your browser does not support the video tag. Download the video.

Displaying logs in the browser

it("should show browser console logs", async ({ browser }) => {
    browser.on("log.entryAdded", entryAdded => console.log(JSON.stringify(entryAdded, null, 4)));

    await browser.execute(() => console.log("Hello Bidi"));
});

Your browser does not support the video tag. Download the video.

Taking a screenshot of the entire page

import * as fs from "node:fs";

it("should screen full page", async ({ browser }) => {
    await browser.url("https://www.npmjs.com/");

    const tree = await browser.browsingContextGetTree({});
    const file = await browser.browsingContextCaptureScreenshot({
        context: tree.contexts[0].context,
        origin: "document",
    });

    fs.writeFileSync("screenshot.png", Buffer.from(file.data, "base64"));
});

Your browser does not support the video tag. Download the video.

Conclusion

While the BiDi protocol remains in the Editor's Draft stage, its potential as the future standard is already clear. Major browsers like Firefox have taken decisive steps toward adoption, announcing the deprecation of CDP protocol support starting in version 129.

By embracing BiDi protocol support, we're empowering our users with:

enhanced test automation capabilities beyond what WebDriver could offer;
freedom from Puppeteer dependencies - eliminating the instability issues we've consistently observed in CDP-based implementations;
Future-proof testing infrastructure by aligning with emerging industry standards

We encourage you to upgrade to the latest Testplane version and share your experience. Should you encounter any challenges, our team is ready to assist through GitHub issue - just create a ticket and we'll help resolve it promptly!

Running on Local Browsers

Thu, 19 Dec 2024 14:00:00 GMT

Testplane is now able to automatically download browsers for running tests locally. Enjoy a hassle-free start with --local option if you don't need remote browser grid.

Previously, Testplane with the webdriver automation protocol could only be launched locally with a manually started selenium-standalone. Now, it is enough to specify gridUrl: "local" in the Testplane Config or run tests with the CLI option --local. In this case, if necessary, the corresponding browsers and web drivers will be downloaded before running the tests, and they will also be launched for further use in these tests.

You can also download the browsers and their web drivers separately using the install-deps command.

Example of running tests on local browser with webdriver automation protocol:

Tag video is not supported by your browser. Download video.

How to use?

Learn more about this in our documentation How to Run Testplane in a Local Browser.

Extension for VS Code

Thu, 26 Sep 2024 19:00:00 GMT

We have implemented an extension for VS Code for Testplane, which allows you to configure Testplane from scratch, run tests, and conveniently work with the REPL mode.

Installation

Install the extension from the VS Code Marketplace or from the extensions tab in the VS Code IDE.

After installation, open VS Code in an empty project and enter in the command panel:

Install Testplane

Running tests

The testing panel can be opened by clicking on the testing icon in the activity bar.

On the left side of the screen, a sidebar displays a tree of all read tests. The tree displays from top to bottom:

the name of the directory with tests (testplane-tests);
the name of the test file (example.testplane.ts);
the name of the suite (test). In the example, describe from the Mocha BDD interface is used;
the name of the test (example). In the example, it from the Mocha BDD interface is used;
the name of the browser in which the test will be run (chrome).

Each element in the tree has a Run Test button. If you click on it at the element:

for a directory, file, or suite, all child tests will run in all browsers;
for a test, the selected test will run in all browsers;
for a browser, one test will run in one browser.

Example of running tests from the sidebar:

The video tag is not supported by your browser. Download the video.

You can also run all tests using the Run Tests button.

From a text editor

If you open a Testplane test in the text editor, a green play button will be displayed next to each suite (describe) and test (it) for launching them. If you click the left mouse button, the test will run in all browsers, and after execution, the result will be displayed as a status icon for the test's pass/fail status. If you right-click the play button, you can run the test in one of the browsers.

Example of running tests from a text editor:

The video tag is not supported by your browser. Download the video.

With the `devtools` settings

In the sidebar of the testing panel, there is also a section titled Testplane. Here you can manage settings at runtime. By clicking the Enable devtools checkbox and subsequently running tests, browsers will launch using the CDP protocol (regardless of what is specified in the config). You can read more about this mode here..

With the `REPL` settings

When you click the checkbox Enable REPL and subsequently run a test (only one test can be run simultaneously in REPL mode), it will be launched in a special REPL mode. You can read more about this mode here.

To display only tests in a specific browser in the tree, you need to enter the tag @testplane:browser:your_browser_name in the filtering input. To get a suggestion, you can simply type @browser. You can also use multiple tags there.

You can also use the following values in the filter input:

a string with the name of the tree element (directory/file/suite/test/browser);
tag @doc - to display tests from the active file in the text editor;
tag @openedFiles - to display tests in all open files in the text editor;
tag @executed - to display only running tests;
tag @failed - to display only failed tests.

Restarting the Testplane Environment

You can restart Testplane using the Refresh Tests button in the sidebar. In this case, the config and tests will be re-read. This will be useful if you have added a new test to a file (watching test files is not yet supported) or if a critical error has occurred. The test tree is automatically updated when the config changes.

Requirements

the Testplane version must be 8.20.0 or higher (tests will not run with lower versions).

Current Limitations

debug and continuous (auto-run) modes are not supported;
there is no watching for adding/removing tests and files;
using custom Mocha interfaces may lead to incorrect display of icons with the play button for running tests from the text editor.

Conclusion

This functionality provides our users with new opportunities:

the ability to run tests directly from the IDE and view the execution results;
the ability to quickly switch to devtools and REPL mode;
automatically pick up changes made to the Testplane config.

Install the Testplane extension for VS Code and provide us with feedback. If you encounter any issues, please visit the GitHub issue — we will definitely help you!

Screenshot testing with Storybook

Thu, 26 Sep 2024 13:00:00 GMT

Now, for automatic visual testing of your components, you only need Storybook with your components and the @testplane/storybook plugin. There’s no need to write any tests anymore.

Storybook is a tool for developing user interfaces based on components. It allows developers to independently visualize components in various states in an isolated environment, separate from other components. This "showroom" is perfect for screenshot testing your components, as this isolated environment makes such tests significantly more stable and faster compared to e2e testing.

With the @testplane/storybook plugin, you can automatically verify changes to your components using screenshot testing without writing a single line of test code. You just need to describe your component in Storybook and Testplane will automatically generate all necessary tests upon execution, run them in the required browsers and provide a visual report for updating screenshots. Additionally, if a play function has been declared for the components, Testplane will execute it before the test begins to set the component to the desired state.

However, if these capabilities are not enough, you can directly describe a Testplane test in the story file, which will be executed as an additional test for the component.

How to use it?

Learn more about this in our documentation Screenshot testing with Storybook. Also you can try it yourself in our example project on GitHub with customized screenshot testing.

Component Testing

Mon, 10 Jun 2024 14:00:00 GMT

In testplane, experimental support for component testing and unit tests running in the browser has been added.

Almost all modern web interfaces are built using frameworks (React, Vue, Svelte, ...) to simplify the creation and reuse of components. It is important to test such components in isolation from each other to ensure that each component correctly performs its function. Just as we write unit tests separately from integration tests. Testplane already supports screenshot testing of components using Storybook, but this tool is not relevant for all projects. Therefore, we developed another option for component testing that does not require the use of Storybook.

This feature can be useful if your project uses React components. At the same time, there are no tests at all or only heavy integration tests are used (i.e., entire pages containing many components are checked). According to the testing pyramid, there should be fewer integration tests because they are more prone to "flaps" and often redundant. Many scenarios can be checked using component tests, thereby reducing test execution time in CI and improving their stability.

Component Testing Implementation Options

Component testing is a type of testing where the logic of a web component is checked in isolation from the web page in which it is used. To perform such a test, you need to be able to correctly render the component. Often, JSDom (used in Jest) is used for this task, which renders web components using virtual rendering in Node.js, i.e., without using a real browser. On the one hand, this works faster (the browser is not launched), but on the other hand, it is less stable because the checks are not performed in a real browser. The second popular solution is to use a very fast dev server Vite, which supports many frameworks (React, Vue, Svelte, ...) and is responsible for rendering components in isolation.

We chose the option of using Vite because this approach provides testing of the page closer to reality (as if it were opened by a user). At the same time, the tests themselves run a little longer than in jsdom. But for us, the most important thing is the stability and reproducibility of test results, so the choice was obvious.

Brief information on how this is implemented

Rebranding

Mon, 20 May 2024 13:00:00 GMT

We present to your attention... Testplane. Our project Hermione has decided to change its name — meet the time-tested product in a fresh look!

We carefully considered all the pros and cons and concluded that the new name — Testplane — best reflects our vision and future development of the product:

We plan to actively invest in the development of the tool in open source. The new name symbolizes a qualitative leap in the development of the tool.
We aim to create a full-fledged brand with a trademark, logo, and corporate visual style. Testplane is a name that both references a "test flight" and can be read as "a plane for testing."

The essence of the product remains unchanged. Testplane is the same project you have known for many years as Hermione, but in a fresh, updated form. To simplify the transition, we decided to maintain continuous version numbering: Testplane v8.x is equivalent to Hermione v8.x.

If you are already working with Hermione, updating to Testplane will take just a few minutes. We designed it as a drop-in replacement:

Full support for existing Hermione plugins.
Understanding of all Hermione options and environment variables.
Full configuration compatibility.
Two binary files (testplane and hermione) for a smooth transition (you can run both as hermione gui and as testplane gui).
Type export for TypeScript, including both Testplane's own types and Hermione's types (including hermioneCtx).

If you haven't tried Testplane yet — check out our documentation and start your exploration with Testplane in just a few minutes!

Thank you for your interest in the project! ✈️

Testplane Blog

Test run selectivity

How to use​

Conclusion​

Testplane vs Playwright: Complete Comparison of Test Automation Tools

Brief Tool Overview​

Key Differences​

Browser and Mobile Device Support​

Visual Testing​

Test Report Interface​

AI Integration​

Extensibility and Integrations​

Scaling and Performance​

Updates and Stability​

Selection Recommendations​

Choose Playwright if:​

Choose Testplane if:​

Testplane MCP

What capabilities does Testplane MCP unlock?​

Significant improvement in test generation​

Browser usage by AI agents​

Installation​

Usage​

Implementation Details​

Time Travel + Testplane UI Updates

How to get the latest updates?​

Time Travel​

Testplane UI News​

Fuzzy Test Search​

New Buttons for Managing Interface Elements​

Other Improvements​

WebDriver BiDi protocol support

How to use?​

What can be done with the new protocol?​

Tracking and intercepting network requests/responses​

Displaying logs in the browser​

Taking a screenshot of the entire page​

Conclusion​

Running on Local Browsers

How to use?​

Extension for VS Code

Installation​

Running tests​

From the sidebar in the testing panel​

From a text editor​

With the devtools settings​

With the REPL settings​

Filtering tests in the sidebar of the testing panel​

Restarting the Testplane Environment​

Requirements​

Current Limitations​

Conclusion​

Screenshot testing with Storybook

Component Testing

Component Testing Implementation Options​

Rebranding

How to use

Conclusion

Brief Tool Overview

Key Differences

Browser and Mobile Device Support

Visual Testing

Test Report Interface

AI Integration

Extensibility and Integrations

Scaling and Performance

Updates and Stability

Selection Recommendations

Choose Playwright if:

Choose Testplane if:

What capabilities does Testplane MCP unlock?

Significant improvement in test generation

Browser usage by AI agents

Installation

Usage

Implementation Details

How to get the latest updates?

Time Travel

Testplane UI News

Fuzzy Test Search

New Buttons for Managing Interface Elements

Other Improvements

How to use?

What can be done with the new protocol?

Tracking and intercepting network requests/responses

Displaying logs in the browser

Taking a screenshot of the entire page

Conclusion

How to use?

Installation

Running tests

From the sidebar in the testing panel

From a text editor

With the `devtools` settings

With the `REPL` settings

Filtering tests in the sidebar of the testing panel

Restarting the Testplane Environment

Requirements

Current Limitations

Conclusion

Component Testing Implementation Options