|
|
Browse by Tags
All Tags » Unit Testing (RSS)
Showing page 1 of 2 (11 total posts)
-
------ Rebuild All started: Project: Components, Configuration: Debug Any CPU ------
Compile complete -- 0 errors, 0 warnings
------ Rebuild All started: Project: web, Configuration: Debug Any CPU ------
Compile complete -- 0 errors, 0 warnings
========== Rebuild All: 2 succeeded, 0 failed, 0 skipped ==========I didn't think I would get to ...
-
By now most people will know about ResolveURL and use it whenever they need to reference a page that may be in a different folder. I still regularly see user conrols that reference images using plain paths though, and they only work when you use them from certain folders. Create a new folder and use the existing user controls in there and suddenly ...
-
I love the smell of green in the morning.
I'm in the middle of a huge refactoring project and although I'm working in VSTS my old habits made me stick to NUnit that the tests were originally written in.
I haven't even looked to see if VSTS will be able to use my tests as-is..but should I even try? NUnit is like an old pair of ...
-
The largest and most complicated Dozing Dogs CMS release was finalized today.
At 13 weeks since our last release, it certainly went over my initial estimate - mainly because I decided to add unit tests for every single stored procedure. With such extensive database changes I really needed their help, and in the end I don't regret the 4 ...
-
In Http objects and Unit testing I introduced you to my Context class that replaces the HttpContext classes such as Request, Response, Session, etc..allowing me to unit test my class libraries without fear.
During some real-world testing on my staging server yesterday I got tripped up by two bugs not trapped by the unit testing. Of course the ...
-
I remember a discussion some years ago at my then current employer that took place (as all great developer discussions do) after our daily pilgrimage to Subway. We even used to make ''Woo, woo!'' sounds as the ''Subway Train'' left at precisely 11:30 each day, but I digress...
The discussion was about unit testing. Where should the tests go, and ...
-
Chris Frazier made an excellent point about my earlier blog ''internal, not private'' when he commented
''Testing privates bad. Testing public api gooood. Makes refactoring lots easier.''
He's right of course, but of course I have A Very Good Reason. Well, no, actually I don't. I have a Poor Reason actually, but that's good enough for now.
You ...
-
I've meant to say this before, but use internal1 for your private/protected methods if you can; it will make them available to your unit tests if you ever decide to test them (and of course you should!)
1 I think Friend is the correct term for you VB users
UPDATE: I may need to clarify this. Here is how I setup my ...
-
Unit testing continues; I've added tests for more than half the code now.
I'm actually only testing methods containing stored procedure calls since that is the current point of unit testing - I want to exercise every sproc to ensure that my latest unicode changes are working. Even without testing every method, it's a lot of work to add tests ...
-
Following yesterday's Unit testing and Caching blog I've decided to spend a little time writing support for all Http-based objects, like Response, Request, Server as well as Context.Items and Cache.
So, now I have a new class called Context in the Utils assembly that replaces every HttpContext.Current reference in the entire application. There ...
1
|
|
|