gerry_lowry-416-992-1615
2008-05-17 19:08:46 UTC
Hello ... although I've been programming since 1967 and am dedicated to quality through design and thorough testing,
automated testing is relatively new to me.
Over time, I suspect I'll get a better understanding of nUnit ... but I'm curious as to what nUnit can and can not do.
Also, because I do not yet understanding nUnit's architecture, I'm not sure when to use or not use nUnit.
Example Scenario
-------------------
Web site testing -------------- validating the user interface
[login screen] =====> [menu] <===> [actions] ======> log out
Manually, I'd launch the login screen, make deliberate errors in user ID and password
until satisfied that the authentication routines, then use several different valid user ID/password
pairs to ensure that legitimate users can log on and off.
I'd manually test every menu choice multiple times. From every menu choice, I test the related actions
until I was satisfied that I'd achieved an appropriate level of robustness. At this point,
the end-users would be asked to try it out and to purposely attempt to break it.
With so much visual interaction required to use applications like the generic one describe above, can nUnit handle them?
Also, can nUnit handle them without one having to write more code than it took to write the application in the first place?
What does/can nUnit do?
When are nUnit's limitations?
When should one use nUnit?
When should one NOT use nUnit?
Thank you in advance for sharing your expertise and advice.
Regards,
Gerry
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
automated testing is relatively new to me.
Over time, I suspect I'll get a better understanding of nUnit ... but I'm curious as to what nUnit can and can not do.
Also, because I do not yet understanding nUnit's architecture, I'm not sure when to use or not use nUnit.
Example Scenario
-------------------
Web site testing -------------- validating the user interface
[login screen] =====> [menu] <===> [actions] ======> log out
Manually, I'd launch the login screen, make deliberate errors in user ID and password
until satisfied that the authentication routines, then use several different valid user ID/password
pairs to ensure that legitimate users can log on and off.
I'd manually test every menu choice multiple times. From every menu choice, I test the related actions
until I was satisfied that I'd achieved an appropriate level of robustness. At this point,
the end-users would be asked to try it out and to purposely attempt to break it.
With so much visual interaction required to use applications like the generic one describe above, can nUnit handle them?
Also, can nUnit handle them without one having to write more code than it took to write the application in the first place?
What does/can nUnit do?
When are nUnit's limitations?
When should one use nUnit?
When should one NOT use nUnit?
Thank you in advance for sharing your expertise and advice.
Regards,
Gerry
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/