What's New (Page 8 of 9)
For VS Code and JetBrains editors, Wallaby’s Test Story Viewer now allows you
to quickly identify and hide repeated sequences of executed code pieces with the
codelens action: Hide repeated entries like this.
intention action: Hide repeated entries like this.
action: Hide repeated entries like this.
action: Hide repeated entries like this.
This feature lets
you focus on the important parts of the executed code and helps you maintain focus.
Some examples of repeated code may be utility functions (such as a logger), code repeated in a loop, and frequently executed functions that are callbacks (such as array’s .filter, .map, .reduce, etc.).
Once the repeated pieces of executed code are hidden from the test story, Wallaby’s Time Travel Debugger will no longer step into the hidden pieces when moving forward and backwards through your code.
Wallaby now supports .svelte files, showing coverage and logged values inside script blocks.
Please note that if you have any preprocessors (e.g. TypeScript) then you will need to ensure that source maps are available for them and enabled in your Svelte configuration in order to get correct coverage and line indicators.
We made significant improvements to Show Value detection when using Show Value, Copy Value, and Debugger on selection. This update enables fuzzy token selection instead of previously having to select an exact token to output. In addition to being able to show values for additional syntax constructs, the feature also now has better support for code transpiled with TypeScript and Babel.
For VS Code and JetBrains editors, Wallaby now allows you to view any number of values (Show Value and Debugger on selection) without changing or editing your code. Inline values now survive
code changes and are updated with their latest values, as you type. A few new commands are available, Clear Value (Escape), Clear File Values (Escape, Escape), and Clear All Values (clears values in all files).
For VS Code and JetBrains editors, Wallaby’s Time Travel Debugger now provides two additional commands to Run Back to Breakpoint and Run Forward to Breakpoint.
Use your editor’s standard debugger breakpoints with these commands to improve your Wallaby debugging experience.
With the help of the Wallaby’s Test Profiler we’ve made incremental runs of Jest tests up to 5 times faster. The default create-react-app generated test takes Jest CLI runner ~430ms in watch mode to run, the same test takes Jest + Wallaby ~80ms.
Our first big feature of 2021 is expected to be a game changer for many of our users. The Test Profiler allows you to quickly and easily get the CPU Profile for any test. No configuration is required, one simple click and you will see the CPU profile for a test.
The first free Wallaby webinar was run on Wednesday, 14th October 2020. If you missed out, you may watch the webinar recording. The feedback from both new and existing Wallaby users was overwhelmingly positive with many saying they learned a number of new tips and tricks.
Wallaby is now available for free for Open Source projects that:
- Are publicly available on GitHub with an open source license.
- Do not provide paid versions of open source software or any commercial services around the open source project (e.g. paid support, consulting, etc).
For VS Code and JetBrains editors, Wallaby’s new Test Story Viewer provides a unique and highly efficient way of debugging your code and inspecting what code your test is executing in a single logical view. The viewer is fully integrated with Wallaby’s Time Travel Debugger, which means you can simply select a variable or expression to see its runtime value. Having the executed code displayed in a single continuous view really cuts down on context switching that you may experience in a traditional debugger experience.