…standing on the shoulders of giants…
After you've used selenium for a while, you'll be familiar with some of the problems. Yep, WaitForElement doesn't exactly cover itself in glory. It is possible to work round this a bit using a static helper for retries. Something like this; public static void MyNavigateMethod(this IWebDriver driver, int retryCounter = 0) { try { driver.DoSomething();... Continue Reading →
My quote-of-the-day, regarding Test Driven Development: I am convinced that it [TDD] can work to your benefit, but it’s not without a price (time to learn, time to implement, and more). It’s definitely worth the admission price, though. Taken from the excellent The Art of Unit Testing: with Examples in .NET by Roy Osherove.
Unit testing is a tricky beast. As with all unit tests it is important to abstract any dependencies – so in the case of EF it’s the data persistence source. This must be handled carefully because EF creates a container that performs the interaction with the data source. Abstracting that container (via mocking or stubbing)... Continue Reading →
During my investigations into this crazy land I have found a few good articles (and many not so good…): http://www.cauldwell.net/patrick/blog/MVVMAndTestingSilverlight.aspx http://silverlight.net/blogs/justinangel/archive/2009/02/25/silverlight-unit-testing-rhinomocks-unity-and-resharper.aspx Both use MVVM and both use RhinoMocks, but in subtly different ways.
When setting up a Silverlight Unit Testing class the following using statements and inheritance must be applied: These are required for the TestPanel and EnqueueX methods (particularly inheritance). For more on the Inner Class Pattern, take a look at the Type Mock training blog.
Excellent step by step post from Justin Angel – what a guy!! http://silverlight.net/blogs/justinangel/archive/2009/02/25/silverlight-unit-testing-rhinomocks-unity-and-resharper.aspx
Mark Cooper 