Testing GUIs and customer tests using FIT

My blog has moved.
You can view this post at the following address:
http://www.osherove.com/blog/2004/9/3/testing-guis-and-customer-tests-using-fit.html
Published Friday, September 03, 2004 10:31 AM by RoyOsherove
Filed under: ,

Comments

Friday, September 03, 2004 8:41 AM by JosephCooney

# re: Testing GUIs and customer tests using FIT

I really didn't like FIT - the idea of having to wrap your real object model in a "test harness" object model seemed like un-necessary work, and a potential place for bugs/ambiguities to hide. Also the "HTML tables as a simple programming language" idea really didn't grab me either. The choice of HTML table seemed fairly arbitrary (bordering on bizzare). A domain-specific language seems like a much better option. Darrell Norton and I exchanged some thoughts about FIT here: http://dotnetjunkies.com/WebLog/darrell.norton/archive/2004/06/02/15230.aspx
however it seems like some people have had more positive experiences.
Friday, September 03, 2004 12:58 PM by nospamplease75@yahoo.com (Haacked)

# RE: Testing GUIs and customer tests using FIT

I absolutely agree regarding NUnitAsp and NUnitForms. NUnit makes sense because you're typically testing the interfaces of your object models. But the other tools are testing UI, which is the thing that is MOST likely to change in a project.

I'd probably only consider NUnitAsp and NUnitForms for ex post facto regression testing (like when you find a bug). I think they are better suited for system testing.
Sunday, September 05, 2004 8:44 PM by Alex Furman

# re: Testing GUIs and customer tests using FIT

It really depends how much time it takes to write a test. You can look on my project on http://home.comcast.net/~furmana/SWIEAutomation.htm. You can visually generate test in a few minutes (C# or VB.NET code).