I have been reading through the various posts and noticed everyone is asking about training from schools. This is great but the schools must be using some books. Not too write too sarcastically, every other certification I have seen has its 2000 page text book. Does any one know any good books to look at that could be purchased for some self training. I am interested in finding out more about this area of IT and I do not want to pay 7 grand for the experiance. I would rather pay the price of a good book.
I have used self-training due to an absence of worthwhile testing courses in my country (New Zealand) and the trick in self-learning is to know which books to read in what order.
I would start off by using Google to find the course notes for Software Testing at the University of South Australia or Kelvin Ross's "Practical Guide to Software Testing" PDF. These are good "starting from stratch" reading.
The next book to buy is the classic "Testing Computer Software, 2nd Edition" by Kaner,Falk & Nguyen. This is a fundamental "keep it on your desk" book and it's relatively independent of any particular methodology bias.
Go back in history and begin by reading Glenford Myer's software testing book from 1979 (I borrowed mine on Interloan from my public library as it is too expensive to buy) and then move onto either Hetzel or Beizer. I bought Beizer's "Software System Testing & Quality Assurance" book 2nd hand for $10 over the net and the testing principles in it have remained unchanged. This gives an idea of where modern testing methods and ideas have descended from.
For specific areas of testing, I have found that I must select modern books that match well to my particular situation and problems. I normally search on Amazon and read the reviews to get some idea of the content and target audience of all books on a particular area. There are a lot of expensive books out there that can be a waste of $ as they are inappropriate so research the books carefully.
Once you have got to this stage, a good help as well is to search QAForums with particular keywords and read about peoples' actual problems and the solutions other people share
(Please don't do those "help I have problem x" posts until after you have done a search - in 9 times out of 10 I have found the search solves my problem or at least makes me realise I'm looking at the problem the wrong way).