InfoQ Homepage Unit Testing Content on InfoQ
-
.NET 4 Feature Focus: Code Contracts
By far the most important feature of .NET 4.0 is support for a language agnostic design by contract framework. When used properly, design by contract has the ability to greatly reduce the potential for bugs in software while at the same time reducing the number of unit tests that need to be generated.
-
Typemock Announces Isolator 5.1.1 and Racer
Typemock releases its latest version of Isolator and looks ahead with a simpler concept. Typemock also introduces Racer, Typemock’s parallel code solution for unit testing.
-
Testing: What Developers Are Expected To Do Versus What They Actually Do
The recent PDC underscored a major disconnect in the testing community. There is a fundamental misconception that developers only need to write "unit testers" and all other forms of testing are someone else's problem.
-
Flex Testing with FlexMonkey
In this post, InfoQ.com discusses FlexMonkey with project founder Stu Stern of Gorilla Logic. FlexMonkey is an open source record / playback tool for testing Flex applications.
-
Unit Testing Workflow Foundation
Windows Workflow Foundation offers some powerful capabilities for those working with data flow style architectures. But these capabilities come at a cost. Unlike traditional batch processing applications, Windows Workflow Foundation does not lend itself to automated testing.
-
Rhino Mocks - Lambda Edition
Version 3.5 of the popular Rhino Mocks .NET mocking framework has been released. This version marks a major change in the API. A new 'Arrange, Act, Assert' syntax has been added as an alternative to the exiting 'Record-Replay' semantics. This syntax makes strong use of lambda expressions and extension methods, among other .NET 3.5 language enhancements.
-
What are the Qualities of a Good Test?
What is a good test? How do we know if we're writing good tests? Kent Beck, Roy Osherove, Mike Hill and others provide some insight.
-
Interview: Erich Gamma Discusses Jazz, Eclipse, JUnit and Design Patterns
In this interview from QCon London 2008, Erich Gamma discusses the Jazz project, why Eclipse has been successful, the strict Eclipse release schedule, JUnit, Design Patterns, how to identify a design pattern, design patterns and the 'Don't Repeat Yourself' principle, the design pattern community, and whether dependency injection is a design pattern.
-
Mockito 1.5 spies on plain objects
The latest release of the Mockito mocking framework enables spying on non-mock objects and introduces a cleaner stubbing syntax.
-
When is Ok to Break the Rules
In “Just Ship Baby” Kent Beck, author of the JUnit Framework, reminds us that the point of all the Agile processes and practices is to produce shipping software. If they’re getting in the way of shipping software – then perhaps you need to break the rules.
-
Interview: Rustan Leino and Mike Barnett on Spec#
Greg Young sat down with Rustan Leino and Mike Barnett of Microsoft Research to discuss Spec#. Spec# is a superset of C# and allows developers to impose contracts on their own code and verify it. This benefits developers by allowing them to find their own errors sooner saving time and resources.
-
JUnit Still Not Dead
JUnit has recently released version 4.5 of the infamous Java testing framework, but is it enough to keep the project in the spotlight? Read more to find what's being talked about regarding the future of JUnit.
-
Moq .NET Mocking Library
Moq is a mocking library for .NET designed and developed to utilize .NET 3.5 features, e.g., Linq expression trees and lambda expressions. Moq's goal is to be simple and straightforward, allowing a natural integration into existing unit tests, instead of forcing developers to rewrite tests or learn extensive Record/Replay mocking frameworks.
-
Pex Automated Exploratory Testing for .NET
Pex is a white-box test generation tool from Microsoft Research. Instead of hand-writing a separate test case for each execution path within a given method, Pex allows a developer to write a single parameterized test method, which Pex will use to generate a suite of standard unit tests to exercise paths within the target method.
-
Interview: Hakan Erdogmus on TDD Misunderstandings and Adoption Issues
In this interview made during Agile 2007, Dr. Hakan Erdogmus, Editor in Chief of IEEE Software, discusses about TDD starting from a study done by Ron Jeffries and Grigori Melnik and published as "TDD--The Art of Fearless Programming" in the IEEE Software magazine. Hakan talks about current misunderstandings regarding TDD's role in software development and the adoption issues it faces.