Home/ Questions/Q 5966317
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T19:46:55+00:00

ASP.NET apps that I’ve developed (on ASP.NET 2.0) have typically been backed by a

  • 0

ASP.NET apps that I’ve developed (on ASP.NET 2.0) have typically been backed by a database; the great majority of the .NET code on the server loads data in the form of a DataSet or SqlDataReader and uses it to databind something like a DataGrid. The meaningful logic is either database dependent or user interface dependent.

In this context, how should I implement unit tests that would be run by a continuous integration server (probably CruiseControl.NET)? Should I set up a test database connection for it to use to test CRUD operations and more complex SPROCs, or should more logic be contained in the .NET code and not in a SPROC? This becomes more complex when there is structure in the database that the application expects to find (such as a Users table in something I’m writing for a CMS).

Also, what are the best ways to do unit-testing of user interfaces? I’ve found NUnitASP, which is now abandoned but mentions Selenium and Watir.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Take a look at the MVP pattern (Model View Presenter). This should allow you to isolate the behaviour of your system and unit test it properly.

    Also, consider switching to MVC (I would go with Fubu over ASP.NET MVC). This will allow you to test controllers and have a more rails-like experience.

    To automate, I use WatiN (like watir but for .NET). On top of it I use StoryTeller (Google “StoryTeller Jeremy Miller”) to present what is happening in a more human readable way and to provide templates for QA to use.

    I would highly recommend against any business logic in sprocs. Stay away from them. Look at the repository pattern to abstract away getting and setting data.

    Hope this gets you started.

    • 0