Grig and Simon are both still suspicious, so here is an example from the test itself: This is Selenium RC in a keyword-driven framework where test data is in the wiki. Take a look at the "code" below and I hope you agree that an explicit test for creating a record is not worthwhile. Any of these could fail in the setup, even though there is no explicit assertion about success: | clickAndWait | link=Accounts | | | type | name | 0sort1account%%start_time%% | | st-submit | | | | clickAndWait | link=Accounts | | | type | name | 0sort2account%%start_time%% | | st-submit | | | | clickAndWait | link=Accounts | | | type | name | 0sort3account%%start_time%% | | st-submit | | | and even if those didn't trigger a failure, these other assertions about sorting would fail in a really obvious way if any of the three records were missing: | open | /nlw/control/account | | | text_like | qr/sort1account.+sort2account.+sort3account/ | | | clickAndWait | link=Name | | | text_li...
QA is not evil