MotioCI For Cognos Upgrade - Best Practice to use

 
Problem:
 
Content is spread over all folders and there is chance to keep getting new reports in Environment while upgrade testing is going on. Creating test cases and dividing in multiple scripts may be challenges and have more manual efforts as testing progress even with MotioCI.
 
Project Test execution approach steps
  1. Identify reports heavily used using Audit Reports.
  2. Identify reports not used in x months and exclude them from list for testing
  3. Move identified reports, queries, jobs, events, portal pages to a base project folders ( no need for application packages)
  4. Create test cases for data validation and scripts for each BIO execution
  5. Run a dry test and identify issues – prompt manual, report long runs
  6. If some reports taking longer time, they need to be parked in subfolder as long running reports and exclude from Reports test cases
  7. Identify assertions to be used for testing - typical is execution time stability and output comparison
  8. Repeat process to identify & fix issues
 
Benefits:
 
  • With this set up, we would know if any new reports are coming in and add them to test suite.
  • Easy to manage testing based on different department and coordination for fixing them
  • This set up can be reused for regression testing for specific report sets for any change in back end and for future upgrades.

Popular posts from this blog

Cognos Excel Text Wrapping Issue - Row Merge and Column Merge

Cognos: How to replace an existing report without breaking links?

How to change package for a report in IBM Cognos Analytics (ICA)?