Test execution results, including code coverage, are displayed and updated in realtime right where you need to see them — in your code editor, next to the line of code that you're editing. Say goodbye to context switching.
The tool is insanely fast, because it calculates and runs the minimum set of tests affected by your code changes, often only a single test needs to be run. No other testing tool is capable of operating on this level.
There is no vendor, API or framework lock-in when using Wallaby.js, because the tool is a plugin for your existing testing/UI framework and IDE. You will always be able to run your tests without Wallaby.js if you need to.
Tests run immediately as you type, on unsaved changes, in parallel if required; no need to do anything manually. Wallaby knows how your code and tests relate, so after a change only the minimum set of tests need to re-run; no other tool is capable of operating like this. No matter how large your project grows, feedback is almost instant.
Inline Runtime Values
See the results of console.log and runtime variables in your editor, right next to your code. Show and copy expression values with editor commands, accessible using keyboard shortcuts. Wallaby's special comment format can also be used to evaluate expressions and includes the ability to measure code execution times.
Inline Error Reporting
Error messages are displayed right next to the code that caused them. Gutter indicators show if the current line of code is the source of an error, or if it's on the execution path of a failing test or error. Editor commands (with keyboard shortcuts) allow you to quickly navigate to the associated failing test or error source.
Inline Code Coverage
Indicators in the gutter of your code editor are constantly updated in realtime to display test coverage so you can quickly see which lines of code are fully covered, only partially covered or not covered at all. Editor commands can be used to toggle uncovered regions to see exactly which parts of your code have not been executed.
Test and Coverage Explorer
A strategic-level view of your project's tests and code coverage is available through Wallaby's locally hosted web application. Open files in your editor from your browser as you explore your tests and code-coverage. Sort and filter by name, duration, passing / failing tests, and code coverage. You can also exclude code from coverage calculations.
Interactive Tests Output
Test execution results are ergonomically displayed in your editor's output window. All tests that are currently failing are listed, along with errors, diffs/snapshots, error stacks and any console.log calls. The output window's hyperlinks allow you to navigate directly to files in your editor, for example to the exact error line, or to a broken test.
Runtime Value Explorer
Wallaby's Value Explorer allows non-primitive runtime values to be viewed and explored in an easy-to-navigate real-time treeview. This feature is great for exploring larger objects and makes debugging with Wallaby easier and faster. The tree can be expanded to any depth and paths / values can be copied directly to the clipboard.
Enhanced Diffs & Snapshots
When errors contain expected vs. actual values, Wallaby displays compact diffs in editor hover tips and in Wallaby's output window. A command allows you to see the diff in a side-by-side view. Jest snapshot test support includes editor commands to update snapshots for your current test, current file, or your entire project.
How much will Wallaby help me?
We estimate that using Wallaby's basic features alone will make your coding 10.84% more efficient and will save you $2396 per year.
But don't take our word for it. See what our customers have to say below and try it for free to see for yourself.
10,000+ companies all over the world, including many Fortune 500 companies, have increased their productivity and output by using Wallaby.js.
Wow, @wallabyjs looks like magic! ✨— John-David Dalton (@jdalton) January 19, 2018
Yes, this is ES modules in Node "just working" with realtime unit test output inlined in @code thanks to std/esm and Wallaby.jshttps://t.co/iCx1IcN0DS pic.twitter.com/NLegC2O5L3
Just tried Wallaby.js and Im a instafan. It needs a bit of configuration (but they have updated repos with sample configurations to get you up and running) but the feedback loop it generates while writting tests/TDD is just amazing.— Jose 'Joshi' Raez 🏳️🌈 (@JoshiRaez) June 24, 2019
Now I need this for every language plz.
Coding with @wallabyjs easily cut my development-to-complete time in half. Can't recommend it enough.— Sean Matheson (@controlplusb) April 4, 2016
Wallaby.js is one of the most absolutely awesome development tools I've ever used. Instant test feedback and editor integration, plus displaying assignment values per-line, and performance all in one. I'll never be able to live without this. https://t.co/qr8n0JeXPl— Brian Bugh (@brainbag) June 19, 2018
I've spent a lot of time using @wallabyjs over the last few days. Such a productivity boost! If you haven't tried it yet, you really should!— Andrew Van Slaars (@avanslaars) September 15, 2017
Success! Got the in-principle go ahead to roll out @wallabyjs at my new company!— Steve Greatrex (@SteveGreatrex) February 15, 2018
I use #VSCode for all my front end stuff at work. It's a great fit for me. In conjunction, I use @wallabyjs to continuously run my unit tests inside the IDE. It's a fantastic extension if you're into your testing.— Jason Evans (@MrClyfar) June 15, 2019
Going to heavily use @wallabyjs /quokka to show live results of examples. Such an amazing tool.— 🎙️ johnlindquist 🎙️ (@johnlindquist) June 18, 2018
I have said this a bunch of times already. It stills needs a shoutout at least once a year.@wallabyjs adds so much productivity. Such a useful tool!— Thomas Sattlecker (@ThomasS09) August 22, 2019
I love Quokka.js and Wallaby.js extensions for @code— Tony Brown ⚛️ ❤️ 💻 👑 (@codemonky007) July 1, 2019
and the import cost plugin which tells you the size of the package you are importing. I'm sure your followers have given many other great plugins but those are my favs!
Using @wallabyjs has to be one of the best developer experience I've felt in quite a long time. Awesome! Wish I learned about it sooner.— Jean-Philippe Sirois (@veksenn) May 9, 2018
Been having fun with @wallabyjs and quokka. So grateful for tools that improve the quality of my dev experience 🙂— ryan (@RyanKois) February 20, 2018
And I love using @wallabyjs when unit testing . It is truly game changing— Jonathan Marbutt (@jmarbutt) June 11, 2019
I struggled for days trying to get a clean unit testing experience for Typescript. Finally tried @wallabyjs and got it working immediately and exactly what I wanted. All I do is open source dev but my time (and sanity) is well worth the price— Phil Scott (@Philco78) June 22, 2018
Just renewed my @wallabyjs license. One of the best tools I've used, would not want to code without it 😃🙏— Adrian Fâciu 🤘 (@adrianfaciu) December 4, 2018
@wallabyjs Just renewed my licence after (nearly) daily use for a year. You’ve made unit testing easy. Thanks & keep up the good work :)— Josh White (@__JoshWhite) May 3, 2019
Hold your horses! I’m writing my second JS test now. My new year’s resolution is taking action. #wallabyjs— Vidar Aune Westrum (@Virrum) January 8, 2019
If your new company is doing TDD, and you guys are not using @wallabyjs, you are definitely missing out! Look into it and spread the word in your team, you’ll be the new hero! The cost of licence is nothing compared to the productivity boost! pic.twitter.com/2NKkbHiwKy— Daniel Ormeño (@danielormeno) April 6, 2019
Unit testing has been pretty painless since discovering @wallabyjs Good work people!— Daniel Douglas (@_geekjuice) January 9, 2019
I use @wallabyjs, it works great in VS Code (our unit tests themselves are mocha and chai).— Mark Kawakami (@skippykawakami) April 16, 2019
Worked on reducing down the 30 second wait for 1800 angular unit tests to run in Karma. Got it down to, well, instant with @wallabyjs :D— Andrew Shelton (@Sheltonial) March 4, 2015
Nice. For me the best tool is @wallabyjs. I can highly recommend it 😉— Simon Hoss (@simonhoss88) May 27, 2019
Since I've bought @wallabyjs my code coverage went sky-high. Never thought that this would happen.— Damian Kamiński (@_dkaminski_) March 21, 2016
1st Choice: Wallabyjs Value Explorer— N Cohen (@ibreathetweets) June 5, 2019
2nd Choice: vscode debugger
This is such an amazing tool, I use it every day and it keeps getting better https://t.co/JSbJVwGfXQ— Dave Taylor (@davetayls) July 26, 2017
WallabyJS just gave me super powers.https://t.co/b9wEC7mIDR— Matthew Thornton (@Thornton_Matt) March 20, 2016
im only writing tests because @wallabyjs is awesooome :)— Arnelle Balane (@arnellebalane) March 4, 2016
I believe that I have to mention at least once a month how freaking awesome @wallabyjs is. Been working with it for 2 years and still love it every day. Worth every penny and great support. Thx @ArtemGovorov— Brecht Billiet (@brechtbilliet) December 13, 2017
Oh yeah! We use it in every @strongbrew_io workshop so far! #tdd
WallabyJS is beautiful.— Jared McCluskey (@Kluskey) May 23, 2019
For me barrier to doing TDD has always been better tooling esp in large projects, @wallabyjs however has changed that for me— Nimesh Gurung (@nimgrg) October 4, 2016
Just bought my @wallabyjs freedom licence. Its rare that a tool can have such a big impact on my workflow so quickly, I highly recommend it!— James Henry (@MrJamesHenry) July 26, 2016
the time has come to renew my @wallabyjs license. I have never spend $100 so happily. It remains my most important tool!— Dave Benjamin (@zpydee) April 6, 2017
@wallabyjs Seriously great tool, esp running only changed tests/code. I have 1000+ tests & Karma was beginning to be really slow. Thanks.— Christopher Carson (@chriscarson) December 11, 2016
Well damn, @wallabyjs is just plain awesome for JS testing and coverage. They can expect to sell us a bunch of licenses soon!— Hilke Heremans (@HHeremans) January 28, 2016
I love your work! Doing original work on a field that's been pretty much stagnant since black/green screens were cool. 🙌— Nir Benita (@NirBenita) March 29, 2017
Thank you @wallabyjs for an amazing productivity boost!— Cathal Coffey (@coffeycathal) January 27, 2016
@wallabyjs is so rapid I now find waiting about half a second for NCrunch quite tedious when switching to my C# tests.— Jamie Humphries (@_jamiehumphries) July 6, 2015
Been leaning on @wallabyjs recently. The inline symbols shown per test exposed some amazing optimisation opportunities (and a few bugs). 🤘— Sean Matheson (@controlplusb) October 30, 2017
First time of using @wallabyjs all day long at my professional work. Just DOPE! Works like a charm w/TypeScript,ES6,Mocha,Sinon,Chai,Atom.io— Jens Krause (@sectore) September 2, 2015
I just did a decently complex refactor on my JS app — and using wallaby.js made it 10x faster.— Bryan Mills (@diffkid) August 12, 2015
Just renewed my @wallabyjs and upgraded to all editors. Will it save me $70 of time this year? It will save me $70 of time *this week*!— Dave Brotherstone (@bruderstein) May 19, 2016
That moment you realise you've forgotten to start @wallabyjs and you've been wasting your time by manually running your unit tests.— Rich Somerfield (@richie5um) November 18, 2016
Most impressive JS test runner I've seen. http://t.co/93a7KYmjxC Worth a good look.— Shawn McKay (@Sh_McK) June 21, 2015
WOW.. 1 minute into @wallabyjs and I'm reeaaally impressed. Now for some Babel ES6/7 preprocessing— Einar Ingebrigtsen (@EinarI) June 18, 2015
Man, @wallabyjs is a great test runner. Good support too. 2 hours from initial bug report to them pushing a fix live. :)— Cody Hatch (@Codayus) June 17, 2015