InfoQ Homepage Testing Content on InfoQ
-
Presentation: The Joys and Pains of a Long Lived Codebase
In this presentation recorded at QCon SF 2008, Jeremy D. Miller shares lessons learned while developing a project over 5 years. He talks about his mistakes, what to avoid and how to design, code and test better.
-
Presentation: Testing Your Presentation Layer
Yehuda Katz shows how to test a web app's UI using technologies such as Johnson (Ruby to Javascript bridge), jspec (BDD for Javascript), Webrat and others.
-
Recommended TDD Tutorials
Recently, Dave Nicolette consolidated a list of recommended TDD tutorials from a discussion on the Extreme Programming group. Here is a sneak peak at the consolidated list with categorization for quickly getting started with Test Driven Development.
-
Dedicated Tester on an Agile Team
The need for dedicated testers on an Agile team has been long discussed and debated. In many Agile teams dedicated testers play a pivotal role where as in others developers double up as testers. A recent discussion on the Scrum Development group tries to revisit the need for having a dedicated tester on the team.
-
Presentation: Gallio, a .NET Testing Automation Platform
In this presentation recorded at QCon SF 2008, Jeff Brown presents Gallio, a test automation platform, and MbUnit, a test automation framework for .NET. He shows how a test framework works on Gallio and talks about the difficulties faced when building such a platform.
-
Pex White-box Test Generator Updated
Microsoft Research has released a new version of Pex, an automated white-box testing library for .NET. Pex v0.11 brings support for Delegates as Parameters, a new Exception Tree View, Stubbed Events, and Recursive Stubs.
-
Return on Investment for Automated Testing
Test automation is often seen as a way to reduce the costs of testing, increase test coverage and effectiveness, and shorten testing cycles. However, the transition to automated testing is rarely fast and never free, there are real trade-offs to be made. Aspire systems has created a test automation ROI calculator and made it publicly available.
-
What’s Planned for Visual Studio Team System 2010
Bill Maurer, Developer Technology Specialist at Microsoft, held a conference presenting what new features Visual Studio Team System 2010 (VSTS) will have in the following key domains: Team Foundation Server, Source Control, Project Management, Testing, Development and Architecture.
-
Book Excerpt: Agile Testing
InfoQ brings you an excerpt from Agile Testing, a book is for testers on an agile team, test and quality assurance managers transitioning to agile development, and agile teams learning how to approach testing.
-
Presentation: The Ethics of Error Prevention
No one wants programming errors. We have many tools to detect and correct errors in code. We also have a number of techniques we can use to prevent the introduction of errors. In this presentation, Michael Feathers t looksat error prevention while posing a number of interesting questions.
-
Which SOA Testing Tool?
Eric Roch asks what makes a good SOA testing tool? He provides a list of criteria that he used to evaluate the range of tools available.
-
Moq 3.0 Released
Version 3.0 RTM of the popular Moq .NET mocking library is now available. Moq 3.0 includes Silverlight support, improved event and property mocking, Pex integration, and improved samples.
-
Interview: Luke Francl Explains Why Testing Is Overrated
In this interview filmed during RubyFringe 2008, Luke Francl explains his position towards testing. While supporting unit testing, he thinks testing is not going to reveal all application defects. Development teams should practice code reviews and usability tests which are likely to discover bugs not visible though other methods.
-
Example Driven Acceptance Testing
Unit and Integration testing often get more importance in Agile teams as compared to acceptance testing. Gojko Adzic and Lisa Crispin suggest approaches to efficiently include acceptance tests as a part of development.
-
Presentation: Testing is Overrated
In this talk from RubyFringe, Luke Francl asks: is developer-driven testing really the best way to find software defects? Or is the emphasis on testing and test coverage barking up the wrong tree?