What's New (Page 3 of 8)
We are excited to announce support for screen.debug() using @testing-library/react-native in Wallaby. This feature allows developers to easily debug their React Native components and views, improving the overall testing and development experience.
Wallaby now supports Vitest when configured to run tests in child processes. When Vitest v0.0.29+ is configured with threads: false, tests are run in a child_process instead of worker_threads. This change in where your tests are executed allows APIs like process.chdir to be used, which were not available when running with Vitest’s default worker_threads. To benefit from this enhancement, ensure your Wallaby and Vitest are updated to the latest versions.
Hover behavior for VS Code has been improved for log values, errors, inline diffs and snapshots. New icon buttons have been added for copying values (logs, stacks, and expected / actual values from diffs) and existing behavior available in hovers has been moved to icon buttons.
Wallaby now supports the latest version of Jasmine (v5.0.0). The latest version of Jasmine included breaking changes that required updates to Wallaby’s integration. To use the latest version of Jasmine, please ensure you’re running the latest version of Wallaby.
Wallaby now supports the latest version of vitest (v0.31.0). The recent update of vitest included breaking changes that required rework of Wallaby’s integration.
Wallaby has been updated to support wslg (Windows Subsystem for Linux GUI). This allows you to run your tests in a Linux environment while using the Windows GUI. This allows you to start your browser tests and have them run from your WSL environment instead of using your Windows version of Chrome. To use wslg, you will need to explicitly configure the path to Chrome with the env.runner property.
Wallaby now supports node.js v20.x. The recent update of node included a number of breaking changes to projects and tools that use ES Modules.
Wallaby now supports the latest version of vitest (v0.30.0). The recent update of vitest included a number of breaking changes due to internal vitest changes.
By default, Wallaby will capture and display any console.log values that are executed by your code and tests. This behavior can now be changed with a new captureConsoleLog setting.
Wallaby now automatically includes support for ES2022 static blocks. This upgrade enables you to now incorporate static blocks, acting as additional static initializers in your codebase.