Skip to main content
Irrevo Best Practices

Creating content migration test plans

Testing the content migration is an excellent way to calibrate the project direction and fine-tune the process before forging ahead with the entire knowledge base. A test should aim to flesh out any sticking points within a particular process.

As part of the design phase, plans are created to break down the migration process into individual test actions for an end user to easily follow. They should focus on productivity and ease of use to make sure the process is as simple and streamlined as possible. Tested processes can target the actual content migration process or processes surrounding content findability, creation, editing, and publishing.

Testing the migration project design

Create separate testing plans and/or scripts to validate that the design meets the needs and requirements of all end users. The testing plan should be specific to the functional requirements that are outlined and not repeat tests that may have been done by the application vendor or other designs that were not part of this project. Each test plan should include a set of use cases, steps or actions for the user to follow, and the expected results. This allows the person conducting the test to clearly see what the test should show and if it passed or failed.

Testing the content creation process

To test the content migration process, the test plan should include a sample of what the new content looks like, the content standard that is being followed, and instructions on how to make the changes. When the content is changing systems, the process will most likely follow that of the new content creation process. If the process involves changing the content within a knowledge management system, the newly designed content standard should be used. 

Other test plans might target system integrations where unit testing would typically be used and created by a group with the Development team. The business analyst who helped create the functional requirements document and requirements list often creates test plans for User Acceptance Testing. They understand the business process it was designed around and the technology behind the functions. The test plans for each process type will look quite different and will need input from the various designers to ensure the tests validate all of the design functions.

Testing the content

Engage a small group of content super-users to test the newly published content. This keeps the testing process more manageable. It is good to establish an efficient communication channel up front like a private feedback forum or community, as well as a spreadsheet to log issues and questions that the group can add to as needed. This allows them to test at their convenience and get alerts when updates are made to the spreadsheet and forums.

Tip: Make sure you understand the audience that will be following the test plans. Someone who is not familiar with the business process will need additional information describing the steps and what they mean.