.NET From Ottawa, Ontario - http://twitter.com/karlseguin/
Browse by Tags
All Tags »
TDD (
RSS)
Sorry, but there are no more tags available to filter with.
-
|
The pains of unit testing the front-end portion of ASP.NET far outweigh the benefits. It's easier and more worthwhile to stick with your domain and data layers. Lately, I've been working on a project that makes heavy use of HttpHandlers. A significant...
|
-
|
We unit test because we think we get more out of it than we put into it. The upfront cost in time, which is paid for in money by our employers and clients, is paid back by easier maintenance and more stable code. Sometimes the payback is great, sometimes...
|
-
|
UPDATE : I solved my problem by marking my method as protected internal instead of just internal. My adventures through TDD land aren't over yet. I decided to follow Joshua 's and Jeremy 's advice and spend some time looking into RhynoMocks. As you may...
|
-
|
Sooner or later during your TDD experimentation, you'll start to creep up against your data layer. I wouldn't be surprised if a lot of new TDD'ers find themselves brushing up against their database sooner than they ought to. I know I did, but try and...
|
-
|
I hate to digress from the raw TDD discussion so early on, but if you're serious about TDD, you have to consider whether continuous integration (CI) is right for you or not. Even if you aren't doing TDD or unit testing, many teams will find CI useful...
|
-
|
The first thing I want to cover in my "learning TDD" track is to not worry about writing seemingly meaningless or uninteresting code. First of all you never know what shape code will take in the future – the simplest of tests might help prevent a subtle...
|
-
|
Unlike many of my CodeBetter colleagues, I'm not the most Agile developer in the shed. Specifically, I've never done TDD for a real system. I'm more of a unit-test-after kinda guy, which often (not always) translates to unit-test-never. When surrounded...
|
More Posts