Release Testing – Content Migration series

Release Testing – Content Migration series

Release Testing – Content Migration series
  • Adapt your testing
  • Look for families of bugs
  • Is the fix worth the risk?

Adapt your testing

Revise the thoroughness of testing up or down depending on the actual quality being delivered. If every revision reveals a new problem, or breaks something that worked earlier, you must be very diligent in testing top to bottom every time. Conversely, if testing shows very solid quality, it may not be necessary to verify every item in a list of sixty.

Look for families of bugs

When a problem is found, determine its root-cause, and then test the system for other errors that might stem from a similar cause. Then decide whether it’s worth fixing. Add the problem to your test plan.

Is the fix worth the risk?

Consider: what is the risk of trying to fix this problem? Might it break something else? Something more important?

Reading more

This article is part of a series discussing many aspects of content migration from an unstructured storage system to a document management system. The overview page is here: Content Migration to a DMS – Articles.

Leave a Reply

Your email address will not be published.