Defining Successful Test Scripts for IBM Cognos Implementation
A key step in a successful IBM Cognos implementation is testing. Many clients struggle with what to include in their test scripts. Here’s a little Lodestar Solution tip.
As you go thru the design phase, make sure all power users have 3×5 sticky notes. As you define your design, write down each process that you believe should be thoroughly tested on a sticky note. Include on it a description, expected outcome, data requirements, and foreseeable issues.
Place the notes on a large flip chart. (I prefer the sticky flip charts on an easel) At the top of the flip chart, write TESTING SCRIPTS. The flip chart will allow you to take it to different conference rooms that you might be assigned.
Throughout the build process, you will identify other test scenarios and add them to the flip chart. When it comes time to define your test scripts, host a team meeting to review all the sticky notes. Organize them by priority and identify any that need to be in sequential order. I recommend numbering them 1 – Critical, 2 – Important, 3 – Average, 4 – Nice to Have. This will help you organize the notes. Review with the team the description and data required to accomplish the test.
When you write the detail test scripts, I recommend identifying the areas you would like to have in a customized user guide. For these test scripts, be very detailed and include screen shots. This will allow you to include them all in a user guide by simply cut and pasting them into one document.
Remember, if you don’t start planning testing from the beginning you will probably miss something!