I know this is not the right forum to ask this question but there are so many people here who are experienced and have faced this issue as myself. So here it goes...
I have been thinking about the points which affect UI testability for sometime. When it comes to unit testing there are specific points like Dependency Injection, usage of Singletons as factors which affect it. Similarly it must be possible to get a set of points which we must be able to do or avoid to help UI testability. I need your help in collecting these points so that it will help us while we think about design for testability at UI level. Some points to get started 1) Building custom controls like grids or tables either from scratch or from available controls. Sometimes I have seen people drawing their own controls which makes testing extremely difficult 2) Auto generation of UI code. Most of the time it leaves us with randomly generated locators 3) Not using normal locators like id, name which makes testing complex. 4) Using technologies which don't have testability in built like Javafx. 5) Highly asynchronous process. Please let me know about your thoughts and challenges you faced in UI testability. Regards, Sai http://code.google.com/p/chrome-watir --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Watir General" group. To post to this group, send email to watir-general@googlegroups.com Before posting, please read the following guidelines: http://wiki.openqa.org/display/WTR/Support To unsubscribe from this group, send email to watir-general-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/watir-general -~----------~----~----~----~------~----~------~--~---
