A collection of agile software testing contradictions.
Most software testing books are a verbose collection of best practices: what you should do as tester to be successful, often in a traditional ‘lessons learned’ format. Best practices are often sold, particularly by consultants, as silver bullets5. I have particular disdain for best practices, they’re not contextual and too black and white for me. I tend to see the world in shades of gray, a best practice in one context makes no sense in another.
Writing books in shades of gray isn’t easy: it’s much easier to write a best practices book with strongly held views about what you consider to be the right approach, and dispel ideas that contradict your own.
In thinking of books in the middle of two views, one approach is to write a book sufficiently nebulous or generalist that it could appear to work in various contexts. But the outcome is weak as people prefer reading stronger views.
Instead I’ve decided to write a collection of contradictory claims about software testing; the practical implications lie somewhere in between. I see this book as a bit of an experiment: I’ve certainly never seen a book following this format before, but who knows, it may create a whole collection of books with contradictions about software development.
Enlaces Públicos de descarga