Wallaby.js is very different from a file watcher. File watcher would run all of your JavaScript tests and it can be very time consuming. Wallaby uses sophisticated dependency analysis and lots of other tricks to only run tests affected by your code changes, no more no less, so even in large codebases with lots of tests the feedback is delivered very fast.
Yep, wallaby can jump to failing test(s), error sources, show error details inline and much more.
Parallel execution in wallaby works fine with browser "state". Imagine running a half of your tests in one browser tab and another one in a second tab - that's what wallaby does but in 6 or 8 or N processes. As long as your tests set up context for themselves and don't depend on each other (and they shouldn't) - it all works.
Yep, wallaby can jump to failing test(s), error sources, show error details inline and much more.
Parallel execution in wallaby works fine with browser "state". Imagine running a half of your tests in one browser tab and another one in a second tab - that's what wallaby does but in 6 or 8 or N processes. As long as your tests set up context for themselves and don't depend on each other (and they shouldn't) - it all works.