Are you already getting good results with Selenium?s command set?

With the variety of commands Selenium offers, I?m surprised at the
requests for things Selenium won?t do.  (Please don?t confuse my
surprise with accusations, as happened with a previous message.  I
appreciate everyones? contribution and am accusing no one of
anything.)   I?m wondering, how much web code is outside the norm,
requiring special testing. Many things should be tested simply by
Selenium.  Objects calling scripts can be annoying.  If we if we put
all our code in custom tags, as some standards suggest for security
and testing, scripts don?t have to be a problem.  

Are you using Selenium rich test command set and finding deficiencies
or do you become obsessed with what Selenium won?t do?  I have a
tendency to the latter.  Are all Selenium changes driven by real
needs?  Or are shops developing queer code that should be trashed?

Poking around, I see a few troubling problems with frames and windows
but lots of things that will work.  New to Selenium, I more often see
too many choices and have to decide which I should use.  Clearly,
when should I click, open, fireEvent, close, goBack, etc?
   
Are you already getting good results with Selenium?s command set?  


        
                
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com