MotioCI for Cognos Upgrade

In MotioCI, regression testing is organized using three kinds of nodes in the Cognos instance tree:
• Projects
• Test scripts
• Test cases

Main Objectives are
  • Ø  To identify any change in SQL ( Data may look same but may cause issue in future if SQL behavior is changed)
  • Ø  To identify any change in formatting
  • Ø  To identify any change in data for predefined prompts selection ( Data should be available) via Output Stability assertion- can be used for same report or reports in different location within or other instance
  • Ø  Any Environment set up issues
  • Ø  Execution Time stability – to baseline performance issues


Projects – You can create multiple projects to focus on specific application folders and packages. It’s good to name appropriately to distinguish them from other projects and all shown at same place ( projects are arranged in alphabetical order). You can use Project_<App Name>  to create project.
Test scripts – To run multiple test cases together. The test scripts can be customized to take only test cases generated for specific folders instead of running for all test cases at Parent level. Email for failure notification, Schedule to run at interval time can be done
Test cases – Each Report can have multiple test cases for different scenarios ( conditional blocks, data flows)

Job/Events can’t be tested as MotioCI is simulating On demand runs.

For Upgrade Report Regression Testing, below are suggested steps
1.      Define content to be tested – decommission old reports/remove duplicates/
2.      Create Projects for each BIO/LOB/Applications
3.      Create Regression Test cases
4.      Create Test Scripts
5.      Run Test scripts
6.      Identify Failures and fix them or redefine scope. Document findings.
7.      Label once all failures are taken into account and create as Base
8.      Create Projects for comparison
9.      Clone test cases/Test scripts to Upgraded Environment with comparison assertions
10.  Run test scripts and identify issues and document findings
11.  Analysis to isolate/rerun to eliminate Environment Issues vs Coding issue

12.  Migrate new contents and rerun test cases in both Environments  

Popular posts from this blog

Cognos Excel Text Wrapping Issue - Row Merge and Column Merge

Below are the properties to set to keep column size and width with text wrapping: Column Merge issue  http://www-01.ibm.com/support/docview.wss?uid=swg21674298 Set the advanced server property RSVP.EXCEL.XLS2007_COLUMN_WIDTH_CONTROL to TRUE for both BatchReportService and ReportService services.        Row Merge issue http://www-01.ibm.com/support/docview.wss?uid=swg21440556 RSVP.EXCEL.XLS2007_ALLOW_WRAPPING_SINGLE_CELL also to be set to TRUE  for both BatchReportService and ReportService services.   Once done, you can set any column width to be fixed and see same result in Excel as well as HTML. Please note that above properties will not be honored if you have unchecked Grouping repeating cells Report property in Report Properties menu. 
Read more

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

Below IBM document explains behavior of copy/move or overwriting impact of objects:- https://www.ibm.com/support/knowledgecenter/en/SSEP7J_11.0.0/com.ibm.swg.ba.cognos.wig_cr.doc/c_gtstd_copy_move_items.html If you copy and overwrite an existing report, the copied report ID and links replace those of the existing report. In this case, you might need to update links, such as links to job schedules. If you move and overwrite an existing report, the existing report ID and links are maintained. In this case, references to the moved entry are broken. However, this doesn't work in all cases and we see drill through links broken in some cases. Best approach in such case is to use cognos deploy method where you update reports in separate folder in same environment and import it to destination location. You can create single export and import tasks to use for all such updates.
Read more

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

In Cognos 10.x and 8.x , this was the simple to handle on Cognos Connection or via Repot Studio interface.  In Cognos 11.0.6, You  need to load classic view (Cognos Connection) to go back to this interface to change the package. In Cognos Cloud environment, we have single environment for Development and UAT. In such cases, when we move content from Dev folder to UAT area, we need to switch to classic mode to change the package.
Read more