229 karma · joined November 6, 2015
If you have to pick only one go with the MIT OCW, and snag a copy of CLRS. I got mine from my local lib. and it gave me more than enough time to work through the problem sets from the mooc.
Docs may be 20, 30, 40 pages long, and out of those only 10 of those may be applicable, but you really can't know until you read them all. Read the manual.
They would find bugs, but often very cosmetic things - not too many bugs in our business logic (and not because of the absence of bugs within our app). It also took way too much time to manage/write the test cases out (~20 hours) since we were building out features so fast.
I looked into Rainforest QA after them. They're product seemed a better fit, but had a bad experience when one of sales guys used there used "retarded" to describe our current qa strategy.
Eventually I decided to dedicate our resources into building a frontend and backend automated testing framework. This was a way better decision, which we actually built out pretty fast.
I have also seen Trello cards work well for recording specs