The Wallaby team has always supported and contributed to the open-source community. In the last month we released our open-source license model to allow open source projects to use Wallaby for free. The license is available to everyone: project owners, project contributors, or even someone not associated with the project who just wants to open the project and play around.
Today we’re excited to announce a new
feature for VS
Code and JetBrains
IDEs called Exclusive Test Run. Use the
Start Exclusive Test Run command or context
menu item to start Wallaby and only run tests for the selected file or folder without making a configuration change.
Today we are really excited to share a huge new feature that our entire team has been working on for the last few months, Time Travel Debugger for Wallaby.js, we are pretty sure you’re going to love it!
Wallaby.js has a new “Test Filtering” feature that allows you to limit the display of inline code coverage indicators and inline run-time values to only the test that you are working on instead of all tests in your project.
Today we are happy to announce the release of a new feature that allows Wallaby users to control when tests are run. Before today, Wallaby would detect both saved and unsaved changes to code and test files and schedule an incremental test run of affected tests. Wallaby now provides the ability to only run when a file is saved; Wallaby will still only run the minimal set of tests based on your code changes but now waits until a file is saved.
Today we are proud to announce that we have added Angular CLI to the list of technologies supported by Wallaby’s automatic configuration feature. This allows you to use Wallaby with Angular CLI, Create React App, Vue CLI and Jest-based projects without any configuration.
Almost since day 1, Wallaby.js has supported Webpack, but as of today we are now offering a new and improved way of running Wallaby.js with Webpack.