A Bible for Software Testing?
An anonymous reader asks: "I'm soon to be starting a position in software testing and wondered (well hoped) if Slashdot readers had recommendations for reading, in terms of dealing with testing from the trenches and management of the process. I've read a number of general software engineering texts, but what I'm looking for is a specific 'bible' on software testing that will get me in the right mindset, before I begin."
Contract software testing is menial labor. You just follow along with a script and report any defects you find (games are the worst types of apps to test BTW, mind-numbing and really kills any enjoyment you get from gaming). I agree it is very easy and boring. Probably why a lot of it is being dumped to India. Career QA professionals are the ones that are writing the scripts, scoping out the tests, setting up the testbeds, etc. This is very fun work to me.
If you want to continue in QA I suggest you look into getting some experience with automated tools. You will do a lot of coding and problem solving with those. It is a good fit for someone who enjoys coding but either is not good enough or just doesn't want to be a full time developer. Also there is a big demand for these skills.
Q.
Haha... I'm in a dumb company with a horrible QA team. The management has a lot of "vision" for the QA team, but no "execution" skills. I agree that testing *could* be fun, but in my past 4 jobs, I haven't found it to be so. Perhaps I am not detail oriented enough. You seem to be, as you say that you have to find all the "nasty hidden corner" areas of your app. Well, best of luck to you and your QA careers (both SuperguyA1 and parent AskSlashdot poster). I know I'll be looking to enroll in school to do something else where I get to problem solve and work with people more.
Second that! I may want to swear at some of our testers when they send my "fixed" bugs right back at me, but they do find important defects (and just as important, they will document the steps & environment necessary to duplicate them). We the developers suggest test cases, but the better testers go well beyond that and design their own test cases that really stress the system.
It's not a job I would want (did enough hardware testing early in my career), but I respect those who are good at it.