Testing is a major activity in any development lifecycle - a large part of a project budget is spent on it. If we want to effectively use it, the ease of testing should be addressed from the early stages of building the system.
Red Gate's .NET Demon is a new Visual Studio tool that continuously tests, compiles, and auto-saves code in the background.
SQL Test is the user interface for tSQLt, the open source unit testing framework for SQL Server. From the SQL Test window, users can create test classes, view existing unit tests, execute them, and view the results within a dockable panel in SQL Server Management Studio.
In the last couple of years terms like Specification by Example, Executable Specifications and Feature Injection have showed up quite frequently in the community, often in relation to Behaviour Driven Development (BDD) or tools like Cucumber or SpecFlow. InfoQ have talked to some of the leading experts in this domain about what these practices are and how they relate to BDD.
Unit testing is a commonly accepted practice in order to deliver maintainable code. This is especially true for a dynamic language like JavaScript and there are currently several frameworks and libraries for a team to choose from. InfoQ had a Q&A with the creators of some of the leading JavaScript unit testing frameworks about their projects and what they offer to developers.
David Starr demoes Pex –a parameterized white box unit test tool- and Moles –an isolation framework-, two .NET tools useful for test-first development.
Scott Allen explains how to create unit tests for applications making use of the ADO.NET Entity Framework 4.1.
Brian Marick discusses the difficulties met trying to maintain tests that are vital to a project’s success, and how mocking frameworks can help, providing advice on writing unit and integration tests
Martin Fowler and Paulo Caroli discuss testing, continuous integration and continuous deployment, as well as DSLs and REST.
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.
