Have you ever wondered if there was a better way to learn refactoring? Martin Fowler’s Refactoring book was a great introductory book on how to clean up legacy code bases, but over the years, what I have found missing in that book is one a set of guidelines that links all the different types of refactoring techniques together into one continuous process. Read more
Learn how Agile development can accelerate delivery of business value and increase market competitiveness in a .net context, while simultaneously improving software quality, requirement traceability, and team collaboration and effectiveness. Read more
TickSpec is a lightweight Behavior Driven Development (BDD) framework. It describe behavior in plain text using the Gherkin business language: “given, when, then”.
Behavior-Driven Development is more than a technique for creating and organizing unit tests. It is also a wonderful way to communicate with customers and users about the software being created. This video demonstrates some techniques and tools you can use to start delivering software with BDD. : Using Behavior-Driven Development frameworks, this session explores ways to create software starting with solid Agile requirements, moving all the way through automated testing. We use .NET in C# and Visual Studio ALM, although none of these exact tools are required to accomplish the goals we set forth.
You will learn the basics of Behavior Driven Development (BDD) and Acceptance Test Driven Development (ATDD) as well as how to use these concepts to bridge the gap between requirements and implementation ? on .NET platform with SpecFlow. SpecFlow is an open source project inspired by Cucumber aiming at bringing pragmatic BDD to .NET.
Ben Hall shows how Ruby testing tools can help with .NET and ASP.NET development and takes a look at RSpec, Webrat, Cucumber, Selenium and others. Also: a peek at using IronRuby for testing .NET apps.
In this episode we are going to take at how to use Pex and Moles for .Net. Unit testing is great, but most free isolation frameworks require that your mocks implement an interface. But what do you do when the class you are trying to mock is static or sealed with no interface. If you can’t modify the class then your unit testing efforts are usually stuck. Moles, the new free isolation framework from Microsoft, supports mocking almost any CLR based class (including sealed and static classes).
This screencast demonstrates how to use Rake to build .NET solution, run unit tests and build documentation. Rake with Ruby is a perfect combination which will eliminate Nant and MSBuild hell.
Learn about DebugAdvisor, a search based tool to find related bugs, and other related information such as people and files, Holmes, a statistical debugger based on coverage data that can be used to root-cause a bug by narrowing down the code path that results in the error, and Darwin a symbolic execution-based tool to root cause regressions.
In this episode we are going to take a look at how to use manual mocks for testing. Often times when creating unit tests we need to work in isolation in order to cover the paths we are attempting to test. When we want to test in isolation you can use a testing technique where you mock out your dependencies. When using Mocks you can either do it manually (what we are looking at) or you can use a mocking framework like Rhino Mocks. Either way you achieve the same results.keep looking »