I am training an engineering fresh out of college to work on testing (both manual and automated testing). What are some possible ways to go about it? (books, videos, beta testing sites, etc.) Obviously I will be using the person on our codebase too, but I am also interested in them gaining a larger breadth of testing knowledge that they can then bring into our project.
closed as not constructive by Walter, Ryathal, JeffO, Dynamic, Glenn Nelson Dec 18 '12 at 22:17
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or specific expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, see the FAQ for guidance.
The approach that I have found most effective with Newbies is to keep challenging them against what they have done or have proposed - make them explain WHY they have done (or propose) something.
This is equally true if their answer is a good one, or whether it's a bad (or not so good) one ... simply correcting them is less constructive and they'll learn less effectively.
Keep asking questions, and make them think for them-self.
I found http://www.softwareqatest.com/ was a great place to start for me, since I was new to testing a couple of years ago. It has beginner and advanced FAQs, examples, and guidance on terminology you can use explore and understand the world of software testing. It also has resources, tools, and even links to books to give you a practical head start if you're looking to tool up quickly. I consider it a reasonably curated one-stop site that a Google search just can't replace easily.
I also found the example workflow in the manual for TestLink http://www.teamst.org/_tldoc/1.9/testlink_user_manual.pdf was incredibly useful as well. I had no idea what a tester's workflow might look like, and it explained some key concepts in a practical way I didn't know until I read it.
"The Art of Unit Testing" is a very good book and is widely recommended.
I would recommended you do something before you start going into all this theory and training; show him good testing practices and show him examples of good automated tests.
If you can show him that you care about these things and explain why they're important, you'll probably go a lot further with him. There's still a certain lack of belief in testing and there are also people writing bad automated tests who claim they care about testing worsening the problem.