Feedback

I don't believe that UI testing is a waste of time. Testing if a button is visible is as important as any other business test. I say this from personal experience. Some of the webforms we developed have an extensive UI business rules that must be tested.

Well, and don't forget that many organizations require software to work in multiple languages, currencies, etc. If you are not testing the GUI (validating the value of the display) then your risks are very high for serious anomalies that can block user functionality -- and if you are not automating those GUI tests, then your costs are enormous.

@Bruno:i agree with you up to a point. I'm not saying you shouldn't test GUI at all. i agree on testing visibility. and try decoupling the business rules from gui as much as possible since this will make your business rules more testable. binding busines rules to a gui clearly violates GUI and BI layer separation. or am i misunderstanding you?

@jay:have to disagree here. the app i was working on is in english, german and french.we never tested the texts them selves. the proper way to do this is to have a localized resource file in which you hold translations. then you can simply test those. and not wasting time doing it through GUI.

In my case what happens is that, for instance, in a webform, a button can only be visible if two textboxes are filled and the values on those textboxes are valid values. These validations are UI business rules. This UI must be tested. Today I was talking to a collegue and we here trying to figure out if this automating tests where uses cases or unit tests.... what is our opinion by the way?

Hi, I´m add some Janus Controls to NUnitForm ( EditBox, UIButton, UIRadioButton and CheckedComboBox ) but it doesn´t show the properties when I write the test, for example: editBox1.Properties. Do you Know Why?Tanks

Performing GUI tests is an important part in creating high quality products. Is not enough to have big coverage on unit testing, you need also to check the logic of user interface. I can enumerate here several cases when having automated GUI tests helps:- check the tab index order of controls- check changes in form state (e.x. enabling/disabling/hiding graphical objects)- check dialogs open- check message box and its text when some errors are catchedThese and many others are vital for a QA acceptance. There are several good frameworks which can be used to perform such tests. I can enumerate here 2 of most used: NUnitForms or GUI Automated Tests from crom-osec. Using a good framework to perform automated tests helped me many times, especially on maintenance phase, when some changes in the code were producing unwanted changes in user interface.