Testing C# and ASP.NET Applications with Ruby
Published January 3rd, 2011 Under Functional Testing | Leave a Comment
The Ruby community has always understood the importance of testing. They strive to make applications more
testable while improving the approaches and tools they use. They have created some amazing frameworks and a series of best practices to support testing. C# and ASP.net developers can take full advantage for their own applications. This session provides an insight into the Ruby world and how you can take advantage to create readable, maintainable and valuable tests for ASP.net based web applications. This video demonstrates how to integrate Ruby frameworks such as RSpec and Cucumber into your application development cycle, and how different frameworks combined with Ruby can solve a number of problems traditionally faced when using C#.
Watch this streaming video from the Norwegian Developer Conference 2010
Behavior-Driven Development in the Real World
Published August 27th, 2010 Under Functional Testing, Unit Testing | Leave a Comment
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.
Download video in other formats and slides
Test-Driven Development – From Painful to (Near) Zero Friction
Published August 17th, 2010 Under Unit Testing | Leave a Comment
Matt Honeycutt doesn’t like development friction and especially testing friction. Over the last several years, his approach to test-driven development and the style of test cases he creates have changed drastically in an effort to eliminate testing frication. In these screencasts, he uses TDD to implement a class in RageFeed. Starting with very coarse, high-friction unit tests, they will show you how you can gradually reduce the friction by creating better tests. Finally, you will see how easy it is to create clean, readable, specification-style tests in RageFeed today.
Watch these videos on TryCatchFail.com
TDD in a Desgin by Contract World
Published November 2nd, 2009 Under Software Testing | Leave a Comment
After presenting some basics of Design by Contract using Microsoft’s SpecSharp framework, Greg Young explains how we can keep the Test First mentality in a Contract First world.
http://www.infoq.com/presentations/TDD-in-a-DbC-World-Greg-Young
Test Driving GUI with Approval Tests
Published October 30th, 2009 Under Functional Testing, Unit Testing | Leave a Comment
This video shows why you want to write unit tests for the perspectives of specifications, feedback, regression & granularity. Then write a GUI in C# using Windows Forms & Approval Tests. ApprovalTests is an open source tool that supports C#, Java, Ruby for unit or acceptance tests.
The Synergy of Code Contracts and Pex
Published August 26th, 2009 Under Unit Testing | Leave a Comment
Manuel Fähndrich and Peli de Halleux sit down for a quick coding session that shows how to use Code Contracts and Pex together. Code Contracts can be used to specify what your code should do, they get turned into runtime checks which Pex can analyze and try to find counter-examples for. This was a fun session with Manuel and really shows the synergy of the two tools/approaches.
Getting started with Pex in Visual Studio 2008
Published August 24th, 2009 Under Unit Testing | Leave a Comment
Nikolai Tillmann and Peli de Halleux give a short tutorial on Pex, an automated white box testing tool for .Net. The tutorial is a pair-programming session where they show us how to get started with Pex in Visual Studio, starting from an (untested) piece of C# code:
* how to use Pex to explore the behavior of any method in your code,
* how to save the exploration results into a unit test suite,
* how to improve the generated parameterized unit tests to leverage Pex code exploration engine.
If you want to follow up the steps on your machine as well,
* Download Pex from DevLabs
* Download the code example
* Ask your questions in the forum
RSS
Twitter