Architecture

Re: ASP.NET unit testing

liammclennan — Tue, 01 Jul 2008 21:35:26 GMT

Judging by the website NUnitAsp is no longer supported. I don't think there is a unit testing tool for asp.net. The closest things are integration testing tools like watin and selenium. Of the two I have had more luck with watin.

Re: ASP.NET unit testing

TATWORTH — Tue, 01 Jul 2008 17:20:11 GMT

The main URL for NUnitASP is http://nunitasp.sourceforge.net/

You might also like to look at http://forums.asp.net/t/1120598.aspx

Re: ASP.NET unit testing

pajocomo — Tue, 10 Apr 2007 19:42:35 GMT

I would say that you could achieve that with some mock frameworks.

I've tested 3 in the past (http://msmvps.com/blogs/paulomorgado/archive/2007/02/17/unit-testing-and-mock-frameworks.aspx) and a reader pointed another one.

Since than, NMock seems to be a dead project and both Rhino.Mocks and TypeMock.NET have had new releases or updates.

--
Paulo Morgado
http://paulomorgado.mvps.org/
https://mvp.support.microsoft..com/profile/Paulo.Morgado
http://msmvps.com/blogs/paulomorgado/
http://www.arquitecturadesoftware.org/blogs/paulomorgado/
http://weblogs..pontonetpt.com/pjmorgado/
http://www.codeproject.com/script/articles/list_articles.asp?userid=201285

Paulo Morgado
Portugal - Europe's West Coast
https://mvp.support.microsoft.com/profile=D4A89909-0CCC-4D8B-8E7B-AB0F3DEB1E66

Re: ASP.NET unit testing

RZaakir — Tue, 10 Apr 2007 18:28:06 GMT

nUnit is cool, but one problem that I've had is testing fileupload controls and repeaters.

Re: ASP.NET unit testing

pajocomo — Mon, 09 Apr 2007 22:46:00 GMT

With a good mock framework (like TypeMock.Net, Rihno.Mocks, POCMock and NMock), almost everything is unit testable.

--
Paulo Morgado
http://paulomorgado.mvps.org/
https://mvp.support.microsoft.com/profile/Paulo.Morgado
http://msmvps.com/blogs/paulomorgado/
http://www.arquitecturadesoftware.org/blogs/paulomorgado/
http://weblogs.pontonetpt.com/pjmorgado/
http://www.codeproject.com/script/articles/list_articles.asp?userid=201285

"bharathirajaa" wrote in message news:1657392@forums.asp.net...
hi, is it possible to do asp.net unit testing using MBUnit........

http://forums.asp.net/84334/ShowThread.aspx#1657392

Paulo Morgado
Portugal - Europe's West Coast
https://mvp.support.microsoft.com/profile=D4A89909-0CCC-4D8B-8E7B-AB0F3DEB1E66

Re: ASP.NET unit testing

bharathirajaa — Mon, 09 Apr 2007 14:03:27 GMT

hi, is it possible to do asp.net unit testing using MBUnit........

Re: ASP.NET unit testing

hlaford — Thu, 16 Oct 2003 03:11:17 GMT

in order to make it testable, you'll need to put it in the page--NUnitAsp reads the HTML output. what exactly are you attempting to test in a private/protected member of a page? my assumption right now is that you might be able to extract that function to another class and test that class.

in general, it is possible to use reflection to read private variables. i remember doing that to read values out of the Context object in the 1.0 framework.

Re: ASP.NET unit testing

neerajjain — Thu, 16 Oct 2003 01:03:57 GMT

Jim ,
I read that you have used NUnitAsp. I have a question about that.

I know we can check web controls value/visiblity in tester class derived from WebFormTestCase. I user Browser.Get(URL) method to load the page then I can set values of textbox and then do click on buttons and also can check the value of controls but what I want is to check value of a private/protected memeber (String or Int) of the page after the click event in tester class. Is it possible at all , if yes, then how? Please help?

-Neeraj

Re: ASP.NET unit testing

toddkennedy — Thu, 14 Nov 2002 13:09:03 GMT

Thanks.

Has anyone used X-unity? Is it better or worse?

Re: ASP.NET unit testing

dreamscape — Thu, 14 Nov 2002 02:38:31 GMT

I imagine you can use NUnitAsp with any editor, from the documentation:

If you're using VS.NET, you can configure your tests to automatically run when you press F5. Right-click your test project (in our case, "GuestBookTests") and select Properties. Modify the properties of the "Debugging" pane in the "Configuration Properties" folder as follows

It seems this is a convenience factor, instead of F5 just doing the normal debug stuff you get the unit test.

As far as this being only implementable in C#, i would venture to guess no. You should be able to write your test classes in VB.NET, Cobol.NET, J#.NET any .NET language should be fine.

No experience, just common sense and reading. I'll let you know once I set this up and test it out.

Re: ASP.NET unit testing

toddkennedy — Wed, 13 Nov 2002 21:41:39 GMT

Does it only work in C#? What about vb.net?

Re: ASP.NET unit testing

toddkennedy — Wed, 13 Nov 2002 21:39:19 GMT

I'm setting up Nunit right now and the first thing it tells me is: "We assume you're using Visual Studio .NET and Internet Information Server."

Will it work fine without the studio?

Re: ASP.NET unit testing

jimski3000 — Wed, 13 Nov 2002 17:53:38 GMT

Some of the advantages of a proper XUnit-testing tool are:

-The cost (free).

-Source code availability.

-Ability to write tests in the same language as the code you're testing (no dropping to VBScript). This is *very* important.

-Very low turn-around time between testing and coding.

But the real point is that unit-testing is such an important activity for some people that the tools need to fit seamlessly into their development cycle. XUnit derivatives are designed to be unintrusive, simple and fast. I can't imagine something like ACT fitting the bill.

And isn't ACT only available with VS.Net?

Jim

Re: ASP.NET unit testing

toddkennedy — Wed, 13 Nov 2002 15:54:37 GMT

ACT records everything as VBScript. This means that you can modify it however you like. I can be easily modified to call dynamic test data.

Re: ASP.NET unit testing

dreamscape — Wed, 13 Nov 2002 11:07:50 GMT

I'm not sure if ACT does this exact thing. I know you can record a browser session and run a test against it. The only thing I've seen ACT used for was stress testing / performance metrics.

NUnitAsp will allow me to keep adding smaller unit tests to the whole test process so we can test across the board as we check in code to make sure we don't break another area of the code.