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."

Comments

Re:get certified, don't worry too much

[Peterl]

Automation can save significant amounts of time and money if the project:

• Has a large enough number of regressions to make the expense of automating less than the cost of all of the regressions.
• Has APIs and/or UIs that are stable enough over the project (and hopefully across versions) to allow the automation to work without lots of maintenance.
• Has management and development behind the automation effort so that time is properly allocated and dev understands the needs of QA.

Re:get certified, don't worry too much

[oiarbovnb]

While you are correct that not all QA jobs involve executing the scripts that someone else wrote, a lot of QA is testing as that is what the discipline is for. Testing software. A QA department, while it can, doesn't have to order hardware, or write test plans. Testers test, first and foremost. You may be in a managerial position of some sort, I don't know. But it sounds like the poster of the article will be doing software testing, as I traditionally think of it, which is reading and executing test scripts. This job is pretty boring, and any temp should be able to do the job as well as I can (or better because they might be happier doing it considering their alternative might be flipping burgers). You are right that I should "improve my skillset and look for work elsewhere," and am planing on doing just that...thanks for the advice though.