Wallaby.js consists of editor plugin to provide tactical level features, such as the realtime feedback and coverage:
and wallaby app to provide strategic level features, such as the realtime bird’s eye view of your project’s tests connected to your editor:
To get started with wallaby.js in your editor, install the plugin, then have a look into our detailed tutorials for:
- JetBrains IDEs (WebStorm, IntelliJ IDEA, PhpStorm, RubyMine, or PyCharm);
- Visual Studio;
- Atom text editor;
- Visual Studio Code;
- Sublime Text.
- Wallaby App.
Along the way you will need to create a wallaby.js configuration file. There are a few sample projects with wallaby.js config files using various technologies to help you quickly create one.
Once you have wallaby.js installed and running in any of the supported editors, you may also use Wallaby.js App to get the realtime bird’s eye view of your project’s tests connected to your editor.
Wallaby.js design is based on a few simple principles:
- In most cases tests should run automatically when your code changes, only the change affected tests should run, and tests should run in parallel when possible.
- Test and code coverage results should be displayed in the code editor in real time, where and when the code change happens; our goal is to support as many code editors as possible.
- Continuous testing should be software-development-technique-agnostic. Whether you are doing classic TDD/BDD, or tests after, or using some mixed approach or something else – as long as you have tests, running them should be fast and easy.
There are other apps and tools to test your application in different browsers, test it across multiple devices and on different platforms, or run your tests in your CI build. The main focus of wallaby.js is to help you write your code and tests faster, without unnecessary context switching.