Manuel Fähndrich and Peli de Halleux sit down for a quick coding session that shows how to use Code
Pex together. Code Contracts can be used to specify what your code should do, they get turned into runtime checks which Pex can analyse and try to find counter-examples for. This was…
I talk to Hadi Hariri about the differences between Behavior Driven Development and Test Driven Development - and why Hadi chooses BDD every time.Full show notes and an article on the same topic can be found at http://bit.ly/msdnpodcast017
In this episode of geekSpeak, Steven Borg shares the merits of using
Team Build 2008 to radically improve the quality of the code you write. Steven gives a great overview of how to set up automated builds and a build server, and the benefits of investing the time to do it right.
In this episode of The Full Stack, Jesse and Jon reboot their windows phone client project using Test Driven Development (TDD) and the Model View ViewModel (MVVM) pattern. Previous episodes focused on getting different technologies such as Windows Phone, WCF, and OData, connected. With a better…
This is a recording of the US Public Sector Developer Dinner for Partners covering ASP.NET MVC held on October 15, 2008 in Reston, Va.
ASP.NET MVC enables you to build Model View Controller (MVC) applications by using the ASP.NET framework. ASP.NET MVC is an alternative, not a replacement, for…
Seit der Umstellung auf das Domänen Modell sind die Unit Tests im Projekt Blog Poll nicht kompilierbar. Um das zu ändern wird im 7. Teil ein Mock Repository erstellt und schliesslich getestet.
Mehr zum Projekt ab Mai auf meinem
Aaron Kowall discuss how to easily test in an autonomous way an application conceived with modular abstractions such as the "layer". Mario and Aaron discuss how to partition the concerns of the application into layers and best practices regarding application
Denny Boynton talks to
Roy Osherove about what it's like to write tests in the real world where we have lots of dependencies, and how to replace them for testing purposes. They also discuss where a tool like
Typemock can come in handy.
I used to work for a company who's core application, I was told, had over 40,000 unit tests (no joke). I asked them if they had a CI process and ran those tests at every build. The answer I was given was "no" because "running a build with that many tests
takes way too long to run…