Pattern 9: Retest when content updated *
AKA:

Back to Diagram 1 - Getting started Back to Diagram 2 - Useability Back to Diagram 3 - Adding detail Back to Diagram 4 - Workflow/security

View sensitizing image - web site with rapidly changing content
Back button gets you back here

You have adopted AUTOMATED TESTING (6) but the content of your site will evolve inexorably. You completed USABILITY TESTING (7) and GET-IT? (8) tests before the site went live.

When content changes there may be unintended side effects that impact upon usability even when the code that is the site has not itself changed.

Therefore

Maintain two sites: one for testing and one for the public. Run usability tests as well as the automated tests against the test site whenever content is updated. If the tests are passed only then transfer the new version to the live site.

To ease regression testing ensure that you STORE CONTENT IN A DATABASE (64).

Discussion - forces - known uses

Some kinds of content change may have no effect on usability but it is difficult to be sure of this unless you test every time the content changes.

When content changes frequently as in the stock of a wine merchant this pattern is particluarly important.

Browse the language What is Wu? Look at an example pattern sequence Structure of the patterns
Comment on Wu Contributors Return to TriReme home page Links to related sites