It seems that a popular approach to QA automation is a quick start to cover a most critical area with automated tests ASAP and then proceed automating other areas of testing. This second phase requires more dedicated tool(s). So, what features are most important for such a tool so that it could be useful for your web application?
- Visual baseline: to compare with results of new test runs
- Smart CSS selectors: to find and interact with CSS elements on a web page
- Ignore from comparison: selecting areas on a page which should not be checked for differences
- Clone, parameterize and invoke tests: reuse existing tests for quick creation of new ones, with the same or new parameters (such as start URL, text entries, login credentials etc)
- CI-friendly: test execution via Jenkins jobs or with the help of any other popular CI tool
- Your own options?