The following articles look at aspects of test design to help structure your tests.
This article appeared in Testing Experience magazine in the March 2010 edition. It discusses the need for intelligent event handling and recovery strategies in automated tests, as well as ways of achieving this.
When automating tests, there are sequences of actions that occur very frequently and can be reused in many situations, there are specific workflows that are only usable in certain circumstances, and there will be groups of sequences that form complete use cases. This article discusses each type and suggests how to design your tests to make the most of these distinctions.
Structuring tests well so that modules are reusable is one of the best design practices to ensure ease of creation and high maintainability. Nevertheless, it can be difficult to know when to write a reusable module and when not to. This article presents examples and their advantages and disadvantages.
When your suite of automated tests begins to grow past a certain level, it becomes incredibly important to ensure that each Use Case you want to execute will be tested - even if other Use Cases have failed. This article looks at how to achieve this.