2007-Jun-15 - QA considerations after code change

After a bug fixed, or a feature added, QA not only verify the bug or new feature, but also should consider: 1) affected modules, 2) other affected QAs, 3) affected part of documents.

For example, say the QA who tests product registration found that the registration URL has changed. So not only (s)he has to test the product registration with the new URL again, but also:

1). Test the new url link in web console and installation wizard.

2). Tell the QAs who test web console and installation about this change.

3). Mark in somewhere that the old Administrator's Guide and Installation Guide (or Quick Started Guide) should include this update in Product Registration section, and Installation section, which has mentioned the registration URL.

This is a simple example, usually the changes are much bigger, especially between 2 versions.

The corresponding documentation changes are often missed consideration. I propose that an OVERALL review is still needed for new version documents, not just review the new feature part.