Introduction: What's New

In addition to this page, you may also follow us on twitter (@WallabyJs) to be notified whenever we release notable features.

Select your editor

The content of this page is adjusted based on your editor of choice. Please select your editor by clicking on your editor’s logo below before proceeding:

Most Recent Major Features and Changes

The What’s New section includes major features and changes that have been made in the last 12-18 months. For older news or more details about minor updates and changes, please refer to our changelog.

Pause Command (12 Aug 2022)

Wallaby’s new Pause command/action for VS Code and JetBrains Editors allows you to pause real-time test execution and hide all related editor artifacts. To resume tests execution and get real-time feedback, use the Start command in VS Code or Resume action in JetBrains Editors. When resuming, only the tests which were affected by your changes while Wallaby was paused will be executed.

Show Line Value(s) / Timing(s) (29 Jun 2022)

Wallaby for VS Code and JetBrains editors has two new commands, Show Line Value(s) and Show Line Timing(s). Simply select the line(s) of code and use the commands to see the values or execution times.

Vitest Integration (BETA) (08 Jun 2022)

Wallaby now includes support for Vitest, from Vitest@0.14.0+. Vitest is a vite-native unit testing framework that was first released in December, 2021. As a relatively new testing framework, the Vitest team are still often making breaking changes within minor releases, which is why our Vitest support is marked as a beta feature. Please report any issues or feedback to us via our github issues repository.

Smart Start (15 Mar 2022)

Wallaby’s new Smart Start feature allows you to quickly start Wallaby and only the test file(s) that you are currently working on will be executed. As soon as you open another test file, Wallaby will automatically run those tests and Wallaby will continue to execute those tests when they are affected by your code changes. Smart Start can be configured to always run a set of test files on start, and you can customize the automatic test execution behavior to run on edit (instead of open), or to never run automatically.

Read more

Resolve getters during logging (11 Mar 2022)

Automatically expanded objects (logged with the special comment //?+) now resolve property getters. So in case of  const a = { get b() { return 1; } }; //?+  the output will be { b: 1 }. If you want to always resolve property getters regardless whether the logged object is automatically expanded or not, you may use the new resolveGetters configuration setting.

HTML output from tests is highlighted using your editor theme and colors (09 Mar 2022)

Wallaby now highlights HTML output for logs and Testing Library errors. Unlike the ANSI colored output in your editor terminal test run results or basic built-in test output support, Wallaby output is highlighted using your editor theme, so all color settings are under your full control.

Previous major features and changes

Our what’s new archive contains the full history of our major features and changes (starting February 2020).

Full Change Log

Our changelog is available in our public repository. Please note that while we update our changelog every few months, we release new versions of Wallaby.js a few times a week (sometimes a few times a day).

Wallaby Roadmap

We can’t promise that we will deliver everything that we list below, but these are the current major features on our roadmap that we expect to focus on over the coming months.

  • Simplifying Wallaby.js configuration process.
  • Implementing better test debugging.
  • Implementing CI server support.
  • Support for more testing frameworks.
  • Adding more features to Wallaby.js App.

Are we missing something? Share your idea or vote for other submitted ideas