Ember and Angular both try to own the entire (frontend) stack, which can work well but usually only if you're building a new app from scratch. In fact, there's been some brief discussion in the React IRC channel about possibly making an easy way to use React views instead of Handlebars inside an Ember app.
Angular has its own share of problems. As I write this, "Things that suck in AngularJS" (https://news.ycombinator.com/item?id=6630156) is on top of the front page of HN. Earlier this summer, I tried learning Angular and gave up because it seemed too hard and I couldn't wrap my head around it properly. Maybe that means I'm too stupid, but it also speaks to the value of creating small, reusable libraries. Angular inundates you with new concepts and confusing vocabulary (e.g., transclusion) and makes it hard to write "directives" (their reusable components), while React's bread and butter is making reusable components and because it's so focused, it does it well.
But now the school is positively flooded with Angular know-how. In fact, the primary author of the ng-book, Ari, is a guest instructor there, and @gdi2290 (lead FE dev at Keychain, huge Angular guy) is a recent alum who hangs out there all the time basically showing people how much easier their lives could have been if they'd used Angular instead of Backbone or Ember.
That said, React components are naturally small and reusable and so should lend themselves nicely to unit testing. Even though I don't think it's particularly limiting now, more robust infrastructure to support testing is a future goal for the React team.
It's almost impossible to see the text over the background.