I guess that I never mentioned that I'm speaking tonight (January 10th 2005) about Unit Testing. If you are in Seattle stop by and say hello. Check out the NetDA website for directions and other important issues.
The Place: Redmond Wa (Microsoft Campus)
The Time: 7:00 PM
The User Group: .NET Developers Association
The Abstract:
Testing your software is a crucial and indispensable part of creating your applications. Are you planning your tests correctly or are you leaving them to the last minute? Or, worst of all, are you not testing your code at all?
In many companies testing is what the 'testers' do, not something that the developer worries about. What if I showed you that creating the right tests would make you a more efficient coder? Would you be more likely to test your code? How about if I illustrated how writing the proper test could help you find your bugs faster? Interested yet?
There are many types of tests you can run on your application. This presentation highlights tests that make the most sense for the developer, NOT the test team.
Test Driven Development is gaining ground in the .NET community. Isn't it about time you learned what the buzz is about? Unit testing is a developer testing discipline that proposes that you write your test cases first — before coding your application. It recommends that an automated test environment be used. Can .NET development benefit from this unit test or programmer test approach? The answer is a resounding yes!
We will see how to integrate unit tests into Visual Studio.NET and review a number of unit testing application including NUnit. Learn what parts of your .NET application will benefit from unit testing and what parts shouldn’t be included. We'll look at tools for creating and restoring test databases. See the difficulties encountered when attempting to test the user interface portion of your application and look at ways to successfully implement a solid test plan.