Wallaby Team Blog (Page 2 of 4)
We recently volunteered our time to assist a group of high-school kids in our community who are new to coding. It was immediately clear that they did not understand the importance of the feedback loop that exists between writing code and knowing that the code does what was intended.
Today we’re excited to announce a really cool new feature called Output Inspector that is really going to improve your debug productivity. Output Inspector allows you to inspect logged values and error messages within your editor in a pop-out code window.
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.
We are pleased to announce that Wallaby’s Test Stories Viewer is now available for JetBrains editors! In case you missed our previous blog post announcing the Test Stories, this is big new feature that our team has been working on for a number of weeks.
Today Wallaby proudly introduces a unique and highly efficient way of debugging your code and inspecting what code your test is executing in a single logical view. The new feature is called Test Story Viewer (initially only available in VS Code).
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.
We are pleased to announce that Wallaby’s Time Travel Debugger is now available for JetBrains editors! In case you missed our previous blog post announcing the Time Travel Debugger, this is huge new feature that our entire team has been working on for a number of months.
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.