One of the most important points that I mentioned to you already is that we'll have to develop guidelines when to do web tests and (above all)
when not.
Compared to UnitTests, maintenance of web tests may be rather costly if you don't do them well. In my experience it is very important that you develop clear and easy to remember guidelines for what should be automated with Selenium and what shouldn't. Imagine you'd have to change your tests whenever you changed a translation string or made some small change in your page design.
IMO what we shouldn't automate:
- texts and translations correct
- images present
- design guidelines compliance
- browser compliance (design)
- anything else that testers and end users will immediately seen anyway
- ...
What we should automate:
- complicated workflows with many branches and conditions
- form fields, especially form field validation
- correct handling of border conditions
- correct display of error messages for error conditions
- browser compliance (workflows, border/error conditions)
- ...