NUnitAsp Uinit Testing

[Patrick.O.Ige]

I came across NunitASP is it good to use and what are the advantages or
disadvantages
Any advice?

[Jon]

Hello Patrick,

The only thing that I don't like about NUnit ASP is that you need to know
the location of all the controls, for example control A, is in control B,
which sits in a cell of a datagrid which sits on a page. If you have a page
that uses many conrols, that are inside one another it gets difficult to
reference them.

Thanks,

Jon

"Patrick.O.Ige" wrote:

I came across NunitASP is it good to use and what are the advantages or
disadvantages
Any advice?

[MiniMe]

You can't test popup windows.
"Patrick.O.Ige" <na********@hotmail.com> wrote in message
news:ut**************@TK2MSFTNGP15.phx.gbl...

I came across NunitASP is it good to use and what are the advantages or
disadvantages
Any advice?

[alex_f_il]

Look at
SWExplorerAutomation(http://home.comcast.net/~furmana/SWIEAutomation.htm)
It supports Popup Dialog Windows, Html Dialog Windows and lots more.

[Bent Kristiansen]

Hi, I have been using NUnitAsp for a while now, and have the following
thoughts.

NUnitAsp is extremely useful when doing Test Driven Development (TDD) on the
web layer of an application. It is also useful for integration testing and
regression testing. Scenario: You are developing functionality for a user
with special characteristics, on step 7 in a registration process. It will
take 4 minutes to login and fill out required forms input before you get to
the page you are developing. Either you need to debug what happens when the
user clicks submit, or you would like to ensure that the functionality on
this page was not broken by the last refractoring; you can go to your debug
breakpoint or regression test this with one click.

The fact that NUnitAsp is not exactly a Unit Test tool but an
integration-testing tool makes it slow to run the test all the time (like you
should with Unit Tests). It is slow because the tool acts like a user on the
application, using HTTP requests. A test often include a login and some
navigation, thus it is more time-consuming to run NUnitAsp tests than normal
NUnit Tests.

NUnitAsp does not have the possibility to test on every ASP.NET event by
default, but it is fairly easy to write extensions to support you need.

--
Bent Kristiansen
bent.kristiansen(AT)bekk.no
"Patrick.O.Ige" wrote:

I came across NunitASP is it good to use and what are the advantages or
disadvantages
Any advice?

[Patrick.O.Ige]

Thx for the info Bent

"Bent Kristiansen" <bent.kristiansen(AT)bekk.no> wrote in message
news:4B**********************************@microsof t.com...

Hi, I have been using NUnitAsp for a while now, and have the following
thoughts.

NUnitAsp is extremely useful when doing Test Driven Development (TDD) on the web layer of an application. It is also useful for integration testing and
regression testing. Scenario: You are developing functionality for a user
with special characteristics, on step 7 in a registration process. It will
take 4 minutes to login and fill out required forms input before you get to the page you are developing. Either you need to debug what happens when the user clicks submit, or you would like to ensure that the functionality on
this page was not broken by the last refractoring; you can go to your debug breakpoint or regression test this with one click.

The fact that NUnitAsp is not exactly a Unit Test tool but an
integration-testing tool makes it slow to run the test all the time (like you should with Unit Tests). It is slow because the tool acts like a user on the application, using HTTP requests. A test often include a login and some
navigation, thus it is more time-consuming to run NUnitAsp tests than normal NUnit Tests.

NUnitAsp does not have the possibility to test on every ASP.NET event by
default, but it is fairly easy to write extensions to support you need.

--
Bent Kristiansen
bent.kristiansen(AT)bekk.no
"Patrick.O.Ige" wrote:

I came across NunitASP is it good to use and what are the advantages or
disadvantages
Any advice?