|visits||member for||2 years, 4 months|
|seen||Jun 25 at 13:47|
Should Selenium 2 WebDriver tests of CRUD operations be self-contained and independent?
Thanks for the answer. This was the general path that I had started going down after writing the question - encapsulating my common workflows to avoid repeating myself, and then coding my tests to ensure that setup proceeded properly before continuing with the verification steps in the test. The Page Object approach seems as good a pattern as any to accomplish this, and to separate my tests' specifications (generally independent, from a logical standpoint) from their implementations (overlapping, with shared workflows in setup and tear down).