Unit Test Checklist – Cognos Development

Developer Name: <Developer> / Date: <Unit Test Completion Date>
Project: <Project Name> / Version #: <Version Number>
Request #: <KM Request Number> / Release: <Release Number>
Checklist – Section A / Developers / Team Leads/Reviewer
Framework Manager / Yes / No / N/A / Yes / No / N/A
  1. List Models and Packages tested:

  1. Is the .cpf filename in the correct format per naming standards?

  1. Has the .cpf been copied to the correct share?

  1. Is the project language ‘English’ only?

  1. Is the model name in the correct format per naming standards?

  1. Is data source connection properly defined and follows naming standards?

  1. Is data source connection pointing to the correct database schema?

  1. Are all the objects arranged alphabetically (top to bottom) within their enclosing objects?

  1. Are all Date/Time items formatted as dates with a Short Date Style and properties resulting in mm/dd/yyyy?

  1. Were all package naming conventions followed?

  1. Were all relationships tested to ensure inner joins will not transparently drop records to the end user?

  1. Does package publish successfully without warnings or errors?

  1. Are package descriptions in Framework Manageras well as Cognos Connection as per standards?

Report Items / Yes / No / N/A / Yes / No / N/A
  1. List Reports/Dashboards tested:

  1. Are reports named according to standards?

  1. Does report name and report title match?

  1. Is report title centered?

  1. Are the Back and Next Buttons removed on prompt page if not used?

  1. Do date prompts use “Edit Box” for Select UI property?

  1. Do report prompts load in under 15 seconds?

  1. Are prompts sorted?

  1. Are prompt values selected displayed on report?

  1. Are page numbers and current date displayed on report?

  1. Is report data formatted properly?

  1. Are report results as expected?

  1. Is no data option turned on?

  1. Have all user classes/roles been tested on secured reports?

  1. Are Cognos Connection descriptions in the folder/subfolder completed on all reports as per standards?

Cube Items / Yes / No / N/A / Yes / No / N/A
  1. List Cubes tested:

  1. Are Transformer models (MDL) named according to standards?

  1. Are cubes (MDC) named according to standards and match cube title?

  1. Are dimension names descriptive and avoid acronyms and abbreviations?

  1. Are measures named according to standards?

  1. Each cube contains no more than 12 dimensions and no more that 10 measures?

  1. All cube dimensions contain less than 1000 categories?

  1. Are all cube dimensions with more than 200 categories broken into hierarchies?

  1. Are measure values as expected?

  1. Do drill-through reports function and return data that matches in count the measure value selected?

  1. Do drill-through reports follow standards and the unit test section above completed for each drill-through report?

  1. Have all user classes/roles been tested on secured cubes?

  1. Are Cognos Connection descriptions in the folder/subfolder completed on all reports as per standards?

Comments – Section B
<Add comments appropriate to unit testing conducted here.>
Testing – Section C
Test Scenario (Team Lead/Reviewer) / Expected Results (Team Lead) / Actual Results (Attach) / Pass?
<Scenario Description> / <Results Expected> / <Result Achieved>

DeveloperDate

Test Lead/ReviewerDate