InfoQ Homepage Software Testing Content on InfoQ
-
StoryTeller and Executable Specifications - Interview with Jeremy D. Miller
Last week Jeremy D. Miller announced a preview release of his StoryTeller project: an open source .NET project for “Executable Specifications”. InfoQ sat down with Jeremy and asked him about what StoryTeller is, how it differs from other tools like Fit/FitNesse and Cucumber, and what the future looks like for the project.
-
Categorizing Tests
What's the difference between unit tests, functional tests, system tests and integration tests? What about developer tests, story tests, and acceptance tests? There seems to be no consensus on naming and categorization of tests although they are central to many Agile development processes. A discussion on the TDD discussion group examines these categorizations and attempts to clear the waters.
-
Debugging Tips for Selenium Test Failures
While Selenium has gained wide acceptance as a useful tool for automating browser-level tests, tracking down the cause of test failures can take significant time. Daniel Wellman has shared two of his best tricks to greatly reduce debugging time for failed Selenium tests.
-
Kent Beck Suggests Skipping Testing for Very Short Term Projects
Kent Beck suggests that on very short term projects, when you're trying to figure out if there is a viable concept, you might do less (even no) automated testing to help get off the ground quickly. This goes against all of the conventional wisdom surrounding TDD.
-
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.
-
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.
-
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.
-
Story Driven Development Recipes with Cucumber
Behavior Driven Development's (BDD) popularity cannot be denied. By simplifying DSL writing, Ruby allowed the birth of many BDD frameworks. Cucumber is one of them and can also be used to test Java, .NET and Flex and more.
-
Details on Using Code Contracts
InfoQ has informed on the availability of Code Contracts for .NET. This time we want to offer more details on using Code Contracts, an important addition to .NET.
-
Code Contracts for .NET Is Available for Download
Code Contracts is the .NET implementation of the Design by Contract concept. While it was supposed to be delivered with .NET 4.0, Code Contracts is already available for download from DevLabs. Contracts impose certain restrictions on using APIs, making programming safer, having more validations and resulting in fewer unexpected errors during runtime.
-
WatiN: Web Application Testing in .NET
WatiN is an open-source library for automating web browsers using .NET. WatiN facilitates automated testing of web applications through browser interaction. The recently released WatiN 2.0 CTP3 allows testing through Internet Explorer and FireFox.
-
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.
-
Spolsky vs Uncle Bob
The last few weeks, a public dispute has been going on between Joel Spolsky and Robert C Martin (Uncle Bob) about Test-Driven Development and about the SOLID principles of OO design. Here is a summary and review of the match.
-
"Classic" versus "Mockist" TDD, Distinction Real?
Hot in the TDD Yahoo group is a discussion concerning the perceived continuum between the "Classic" and "Mockist" TDD. Steve Freeman, Nat Pryce, Michael Feathers, Dale Emery, and many more discuss terminology and describe their approaches. The discussion also debates whether there even really exists such a continuum, and if so, what distinguishes the approaches that represent it's extremes?
-
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?