“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
This video shows how Selenium, integrated into a FitNesse framework can extend an organization’s ability to create more automated test cases without the need for Selenium programming while expanding the ability to test across all popular browsers.
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.
This a directory of open source and commercial software tools for load and performance testing with reviews and resources. http://www.loadtestingtools.org/
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.