Tracking change and innovation in the enterprise software development community
JProbe Freeware,
an Eclipse plug-in,
diagnoses
memory issues
quickly & easily.
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
QCon San Francisco
Nov 19-21:
+ 80 sessions & tracks
Register now
and Save $400!
In this presentation filmed during QCon London 2007, Nat Pryce and Steve Freeman talk about TDD using Mock Objects. In their opinion, Mock Objects improves the software design and makes the code more easier to maintain and adapt to changing requirements.
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 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.
Iterative and continuous are terms that are often used in reference to testing of software. This new InfoQ article takes a look at whether the same concepts can be applied to performance tuning. Along the way topics such as tooling and mocks are discuss in regards to how they need to be adjusted for performance in respect to testing for functional requirements.
Developers familiar with Test-Driven Development would like to continue their familiar Red-Green-Refactor cycle even when working with Stored Procedures. Cory Foy shows how to use Visual Studio for Database Professionals and inclusive tools as a framework for performing database unit tests.
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.
In this interview from QCon San Francisco 2007, Cédric Beust discusses designing and architecting for testability, problems that hinder testability, test-driven development, the "Next Generation Testing" book, performance testing recipes, and testing small, medium and large codebases.
Writing a test makes you clarify your ideas about what needs to be done, and making the test pass means that you know that you've added a little more functionality today. Having a comprehensive suite of tests gives you the confidence to get on with things because you can tell when you've broken the system, and tests that are difficult to write show you where you need to improve.
Agile communities consider stories “done” when the acceptance tests (also called story tests) are shown to the customer. Originally, this was a manual process, but in recent years, several frameworks have been created to automate this process, providing acceptance testing all the benefits of automated unit testing. One of the most popular of these if called FIT, created by Ward Cunningham.
This book guides the reader on crafting their own agile adoption strategy focused on their business values and environment. This strategy is then directly tied to patterns of agile practice adoption that describe how many teams have successfully (and unsuccessfully) adopted them. Business values are also a component of these patterns so your adoption is always focused on addressing your particular environment.
