Not everything in programming is fun
I never used that framework, don't really know how hard is it (or simple), but I do think unit testing (and other types of tests) are important to get better software. But it is like charlie said, you need to find the right balance and not everything in your code needs to be tested. If you take the "traditional" approach of writing the test before you write the code, for every function, method, class, whatever you implement then it's going to be a long and boring thing to do, but if learn how to write proper tests and choose those areas of you code that benefit from it, the all project will go smother.
Personally, I don't write the tests first, but writing test has both the benefit of allowing me to click a button and see if any of the latest patches caused errors, or if the git merge caused some side effects that I did not find while merging (when you have several programmers it's easy to miss a rouge line of code).
As for professional programmers, well I see professional programmers do a lot of mistakes, I develop software for a living and I can say that I have made my share of mistakes and just because I do this for quite some time doesn't make me all knowing (nor anyone else)
. I never used or have found the need to use any JavaScript framework other than the usual jQuery + plugins combo yet, this month as a requirement I was forced to use Backbone.js, if you'd asked me last month I would say I had been developing for 4 years without ever needing such thing, now I can't really understand how I could develop without the framework
If you're new to unit testing I suggest you start small, add unit testing to the functions or method where you find a bug so that the bug doesn't return and go from there, once you start using you'll see if it is something you need or if you can live without it.