Content tagged with: unit testing
Amanda Laucher and Josh Graham present at an introductory level some of the most important elements of the .NET ecosystem: F#, M, Boo, NUnit, RhinoMocks, Moq, NHibernate, Castle, Windsor, NVelocity, Guerilla WCF, Azure, MEF.
Continuous integration is a great way to keep your code base organized and well tested. But when a test suite takes so long to run that developers stop running it before every commit, they lose their constant feedback loop and quality drops. In this talk weâ€™ll explore methods of speeding up the test suite so that developers can be confident about the code theyâ€™ve written before they share it with the team. Weâ€™ll start with quick cheap fixes, like optimizing your operating system, that can yield drastic results (like cutting …
Steve Freeman proposes advice to write good tests that make development easier avoiding adding code that is hard to maintain. This presentation covers: test readability, complex test data, test diagnostics and test flexibility.
How to get started with TDD? Test-First Teaching is an innovative teaching approach that is gaining widespread adoption. Sarah Allen talks about how she teaches Ruby and Rails through a test-first approach. She demonstrates test-first teaching and then discuss how to turn the corner from simply making tests pass to how to use a test-first approach to software design.
Video Producer: East Bay Ruby Meetup Group
SharePoint Services are challenging for unit testing because it is not possible to execute the SharePoint Service without being connected to a live SharePoint site. For that reason, most of the unit tests written for SharePoint are actually integration tests as they need a live system to run. In this session, we show how to use Pex, an automated test generation tool for .NET, to test SharePoint Services in isolation. From a parameterized unit test,Â Pex generates a suite of closed unit tests with high …
As part of his talk on integration tests J.B. Rainsberger talked about how contract tests can be used to test the interaction between classes when using a mockist approach to developer testing. He wondered aloud if it would be possible to write these kinds of tests using abstract classes and JUnit 4. The answer is yes, with some caveats, as Ben Rady demonstrates it.
Video produced by Ben Rady
Michael Feathers defines legacy code as “code without tests.” There’s a major qualitative difference when working on code without tests. Feathers’ job is to move software teams from their current process to a test-driven development process. In this interview he also discusses functional programming and other important paradigms that developers should consider.
Video source: Dzone.com
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 Stub out dependencies using a wrapper class.
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.