🐛 Bug fixes

• show loader immediately after click to run button in tree action bar

🐛 Bug fixes

• correctly send required modules via cli option require to run method of Testplane in gui mode. In order to correctly require user modules in master and worker processes in Testplane (#755)

🐛 Bug fixes

Add fallback for timeline player if snapshot file is broken

🐛 Bug fixes

Fix --tag option in cli for gui mode

🐛 Bug fixes

Fix a bug in the configuration for the timeTravel option.

This release adds tags support for Testplane and Playwright. You can now see your test tags and filter by them.

🚀 Features

Tags

Here is an example of how tags look in a test. You can see them on the right side of the test title. A tag with a yellow color means it was added dynamically during the test run using the addTag command.

To filter by tags, you can either:

• Type the tag name starting with the @ symbol in the filter field.
• Or simply click on a tag directly in the test list.

Example of tests with tags for Testplane

describe("test tags", { tag: ["common"] }, () => {
    describe("test tags", { tag: ["main"] }, () => {
        it("Feature A", { tag: ["desktop", "uniq"] }, async ({browser}) => {
            await browser.addTag("dynamic tag");
        })
        it("Feature B", { tag: ["desktop", "smoke", "slow"] }, async ({browser}) => {
            // test...
        })
        it("Feature C", { tag: "old" }, async ({browser}) => {
            // test...
        })
        it("Another test", { tag: ["smoke"] }, async ({browser}) => {
            // test...
        })
    })
})

For more details see documentation about tags in Testplane.

This release introduces hotkeys for the most-used UI features, ability to copy and run tests using buttons in the suites tree and improves legacy URLs handling.

🚀 Features

Hotkeys

We're excited to announce hotkeys covering the most popular features, with more to come in the future!

Fast tree actions & test name copying

A long-awaited feature for quickly running all tests in the given suite is now available!

We've added ability to copy suite name with a single click as well.

URLs improvements

Last, but not least, working with URLs is now a lot better:

• Legacy URLs are now understood by New UI and are transformed automatically:

  Old format: ?testNameFilter=some-test-name&browser=chrome&strictMatchFilter=true&retryIndex=0&expand=all
  New format: /#/suites/a23f11/chrome/0/some-state
  

• When browser has multiple version, but in query params browser=chrome is specified, all versions will be selected instead of none before
• A small tag with browser version is displayed for browser tree items having more than one version
• Fixed issues with browsers select being empty

This release contains features that may be useful for plugin developers.

🚀 Features

• Added CollapsibleSection component to Plugins SDK. Use this component in your plugins to match the visual style of collapsible sections found on the test result page (e.g. Actions or Metadata). This component also remembers user preferences (collapsed/expanded) and applies them when switching tests.
• Added result_meta extension point to New UI. This lets you embed your components right on the test result page.

🚀 Features

New url format

Previously, we had URLs on the suites page like this:
suites/${testId}/${state}/${attempt}

And on the screenshots page like this:
visual-checks/${imageId}/${attempt}

Now we have a common format for both pages. We also changed the test name to a hash of the test name:
${suites | visual-checks}/${hash}/${browser}/${attempt}/${state}

Example of the new URL:
http://localhost:8000/new-ui#/suites/26f8dee/chrome/0/main
Before it was:
http://localhost:8000/new-ui#/suites/badges%20badge%20example%203%20chrome/main/0

🚀 Features

Custom badges for tests

Now you can set custom badges for every test. Each badge can have a title, link, and icon. See the screenshot for an example and read the documentation to implement it in your project.