Geek Answers Handbook

Device Testing User Interface. What is an effective way?

I have a client / server accounting and calculation application in which there are several input forms with complex data verification rules. I find an effective way to do unit testing of the user interface.

For complex validation rules, I mean:

  • "Disable the X button if I insert a value in the Y text box"
  • "Enable combobox if I insert a value in the text box" ...... ......

The most promising template I found was suggested by M. Fowler ( http://martinfowler.com/eaaDev/ModelViewPresenter.html ).

Do you have experience testing user interface modules? As a technology stack, I use: .NET 3.5 and the Windows Widget Library.

+5
source share
5 answers

I would not call it "unit testing" for sure, but I had some success in performing automated tests with the WinForms user interface, as well as in the web interface using WatiN.

Assuming you can get the window handle of the application you want to test, you can script to extract a lot of C # code to test the functionality of the user interface.

, , . , , - , . , , .

, , , . , , . , , , , , , - , , .. QA , , , . , .

, , , , .

, , , , . , , , , , , .

+5

, .

MVC/MVP, , - , , WinRunner QTP, .

+3

, . . . , Mercury ( HP) Quality Center Performance Center. , Selenium.

- , eachother.

+1

:

* "Disable button X if I Insert a value in textfield Y"

, , . , Y ; Y X_ENABLED == false, Y X_ENABLED == true; , X_ENABLED == true, View . , , . , .

+1

Without test verification, the user interface is, as others say, a pain. I would like to add that the new feature of Team Foundation 2010 Test and Lab Manager is a great way to do manual user interface testing and automate subsequent tests. It is smart enough to recognize GUI structures when running tests, at least for WinForms, WPF, and websites.

0
source

More articles:


All Articles