Tag:content migration

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…

Read more

Test Planning – Content Migration Series
Test Planning – Content Migration Series

Test strategies for error detection: Use end-to-end release test scenarios. Test all aspects of the imported solution. User testing for business data issues. Burn-in testing. Numeric tests Use numeric tests to find omissions based on unexpected causes. There should be 28 files in the A folder, 61 in the K folder, 4 in the Z…

Read more

Designing large-scale conversions – Content Migration Series
Designing large-scale conversions – Content Migration Series

Here are our four top laws-to-live-by for designing any large-scale data conversion or content migration: Develop Specifications. Design for subset runs. Know how to roll back. Report errors early, don’t hide them. Develop Specifications Includes: functional specifications, technical specifications, tool configuration plan, test case design, and deployment plan design. Refer to the best practices section…

Read more

Development – The Four Commandments (Content Migration Series)
Development – The Four Commandments (Content Migration Series)

Here are my recommended truisms for IT development tasks, particularly in the context of Content Migration. Document new design assumptions. Question stupid approaches. Validate deployment approach with timing numbers. Use challenging artificial unit test scenarios.