This is the third part of the three part series that deals with the issue of faking test data in the context of a legacy app that was built with Microsoft's Entity Framework on top of an MS SQL Server database – an architecture that can be found very often, and that originally came up in the broader context of writing User Acceptance Tests. It shows how you could handle such a scenario with the NDbUnit framework.
This is the second part of the three part series that deals with the issue of faking test data in the context of a legacy app that was built with Microsoft's Entity Framework on top of an MS SQL Server database – an architecture that can be found very often, and that originally came up in the broader context of writing User Acceptance Tests. It shows how you could handle such a scenario with the Typemock Isolator tool.
This is the first of a three part series that deals with the issue of faking test data in the context of a legacy app that was built with Microsoft's Entity Framework on top of an MS SQL Server database – a scenario that can be found very often, and that originally came up in the broader context of writing User Acceptance Tests. It describes a sample application, discusses some general aspects of unit testing in a database context, and also some more specific aspects of the here discussed EF/MSS
A presentation about the MSTest framework (aka. Visual Studio Unit Testing), some additional tools (e.g. Moq, Moles, White), how this is supported in Visual Studio, and how it integrates into the broader context of a TFS environment.
These days, JetBrains (the manufacturer of ReSharper (R#)) released the beta version of a new code coverage tool – dotCover. Here are my first impressions about it…
Usual opensource mocking frameworks can mock only interfaces and virtual methods. In contrary to that, Microsoft Moles can ‘mock’ virtually anything. Here's a little overview over this framework, together with a suitable Gallio extension...
At the moment, this blog post only is kind of a stub. I need it as a target for testing...
Shows how to patch the error that is encountered with the Selenium web testing framework when running it against the latest version of the Firefox browser (3.6)...
Most people - even the overwhelming majority of programmers - would say that the main activity of a software developer is "writing source code". But this is a fatal misconception - about 75% of all time and money (sometimes even more) is spent on some sort of maintenance activity. Far too little effort goes in the future maintainability of a software product during actual development, which in turn leads to software systems that cause substantial technical and financial problems..
Sometimes, it seems just too complicated or expensive to test-drive a certain component in an ASP.NET MVC context, or it would require the use of some browser automation framework. To make testing easier in such cases, this post introduces a Gallio/MbUnit test fixture that builds on top of a framework for integration testing ASP.NET MVC applications without the need for any browser or server, but still running in the real (non-mocked) ASP.NET runtime...
A few days ago, a new version of Gallio was released, my favorite Test and Automation platform. Although the official version number suggests only a small progression, it actually is a major upgrade that brings a wealth of new features. This is a first look at the two features that attracted me most...
Almost every software project comes with a database. But although this is quite common, managing database related tasks is not very handy from the development point of view. To make life somewhat easier, this post demonstrates a way to automate sql script execution for MS SQL Server, using the Gallio Automation Platform.
In some scenarios, you may have a database that contains text data in a column which is restricted to a certain set of discrete values. In such a case it is a good idea to use an enumeration for representing these data in your domain. This post demonstrates an easy and effective way to put this mapping under test.
Having an enum in code that corresponds to a database table is a common scenario in enterprise application development. - For example you may have an 'OrderStatus' enum in your business logic and a corresponding database table 'ORDERSTATUS' in your database. In such a scenario the enum-table relation might be at risk to go out of sync. This post introduces a simple but useful unit test fixture, that keeps an eye on this for the entire project lifetime...