Comments for Nizar's .NET Blog

Comment on Integrating TypeMock with ASP .NET Unit tests by ulu

ulu — Sun, 07 Mar 2010 15:38:45 +0000

My guess is that the Visual Studio’s tests are executed in the separate process (WebDev), while Ivonna runs in the same process.

Anyway, Ivonna is targeted at different scenarios. For example, how do you test a postback with VS Studio ASP .NET Unit testing?

Comment on LINQ : Implementing IN and NOT IN by Nizar

Nizar — Wed, 17 Feb 2010 19:06:42 +0000

What is not in Entity Framework model?

Comment on LINQ : Implementing IN and NOT IN by Janaranjan

Janaranjan — Tue, 16 Feb 2010 17:37:38 +0000

Nizar,

This is not working in Entity Framework model for some reason.

Comment on Am I officially a “nerd”?? by Nizar

Nizar — Thu, 11 Feb 2010 16:50:45 +0000

Depends on what kind of testing you’re doing. If it’s unit testing, then you should stub out the DB layer for at least the following reasons. 1. You have more control over the fake data, 2. There is no reason to run all the logic is the DB layer since you are unit testing. 2. Your unit test will be much faster.

If you are doing an integrated test then yes you should hit the DB and run all the logic in between that.

Hope this helps!

Comment on Am I officially a “nerd”?? by Nisar

Nisar — Thu, 11 Feb 2010 03:02:56 +0000

what is the best way of testing, should you go to db and pull data or stub/fake data?

Comment on Refactoring for Unit Testing by Nizar

Nizar — Sun, 07 Feb 2010 19:12:23 +0000

Yes, you’re right. Thanking you for pointing that out. I’ll make the correction.

Comment on Integrating TypeMock with ASP .NET Unit tests by MrBarns

MrBarns — Sun, 07 Feb 2010 02:49:10 +0000

Hey, I found your blog while searching on Google your post looks very interesting for me. I will add a backlink and bookmark your site. Keep up the good work!

Comment on Refactoring for Unit Testing by krislig

krislig — Sat, 06 Feb 2010 11:24:24 +0000

How do you inject mock objects? Because I don’t see them in constructor or method call in tests code.

I think that assert should be something like this:

CustomerService svc = new CustomerService(123, custManager.Object);
Assert.IsTrue(svc.CanPurchaseProduct(1, prodService.Object));

Correct me if I’am wrong.

Comment on Refactoring for Unit Testing by Nizar

Nizar — Thu, 04 Feb 2010 18:19:18 +0000

To be clear refactoring should be done often and whenever necessary. A general rule of thumb is: If you’ve had to workaround a piece of code for more than 3 times, it’s probably time to refactor it. In this post, I am simply pointing how refactoring can be used to make existing code unit-testable.

Comment on Refactoring for Unit Testing by Adam

Adam — Thu, 04 Feb 2010 05:13:05 +0000

Hey. I don’t normally leave comments, but I just wanted to say thanks for the great information. I have a blog too, though
I don’t write as good as you do, but if you want to check it out here it is. Thanks again and have a great day!

Commercial Carpenter’s Tool List