Software Testing Articles, Blog Posts, Books, Podcasts and Quotes
Some authors are good at presenting theories but unable to connect them to practice. Other are good at telling stories from the trenches, but without being able to produce an analysis of the situation and propose some solutions. On the less examined domain of agile testing, Lisa Crispin and Janet Gregory are, luckily for us, presenting a book that covers both the personal experience of being a tester in agile projects and a conceptual vision of the place of quality assurance in software projects. Thus you will find in this book “stories” that comes from past projects and “mind maps” that helps to have a high-level vision of the material of each chapter.
“We define an agile tester this way: a professional tester who embraces change, collaborates well with both technical and business people, and understands the concept of using tests to document requirements and drive development. Agile testers tend to have good technical skills, know how to collaborate with others to automate tests, and are also experienced exploratory testers. They’re willing to learn what customers do so that they can better understand the customers’ software requirements.” Source: “Agile Testing”, Lisa Crispin and Janet Gregory, Addison-Wesley, 2009
Testing a GWT application seems daunting at first, since GWT application code runs as Java instead of JavaScript. However, using these testing components to thoroughly test application is actually quite simple, and what’s more is that you can apply strong design patterns to your code that will keep test cases concise, effective and maintainable. This article describes testing methodologies and design patterns we can use to test GWT applications.
This post discusses about the fact that software testers don’t have responsibility for software quality any more than anyone else in the development team. Everyone has that responsibility.
Most developers think that the most beneficial part of using test-driven development (TDD) are the tests. But, when done right, TDD improves the overall design of your code. This installment in the Evolutionary architecture and emergent design series walks through an extended example showing how design can emerge from the concerns that float up from testing. Testing is only a side effect of TDD; the important part is how it changes your code for the better.
This post presents good practice for efficient UI test automation.
The article “Writing Testable Code” presents practices to write more testable code with many examples in java, going a step further than just TDD.
