Dashboard Testing

1. Introduction

The aim of this article is to describe the Dashboard Testing Phase of the Dashboard Development Lifecycle. It consists of 3 phases:

• Individual Testing through the form of a checklist

• Peer-Review

• UAT

2. Individual testing

I have tried to divide the criteria into 4 main categories:

1. Layout and Design

2. Data Validation

3. Performance Testing

4. Permissions and Distribution

2.1. Layout and Design Tests

1. Verify the report layout as per the specification

2. Verify that there is a DPD Document completed and signed off

3. Verify the title of the report is correct

4. Verify the alignment of objects (charts, KPI boxes and matrices) are per specification

5. If the dashboard has matrices or tables check if the data is displayed in the proper format, rightly aligned and grounded and that the column headings are correct

6. Verify report creation date and last updated date

2.2. Data Validation

1. Ensure the OLAP cube represents your ERD

2. Make sure it's updated on a schedule

3. Verify if all the calculations on reports are correct (Totals, Averages, Max, Min) against the database tables

4. Verify if data satisfy the filter conditions correctly (Date Ranges, Groupings and other filters that the dashboard may have)

5. Make sure that the table field names are using the naming conventions agreed by your company

6. Check the table joins of your tables

2.3. Performance Testing

1. Check how much time your OLAP cube takes to reprocess and it's not exceeding the time given requirement

2. Verify how much time it takes to download the dashboard (export it)

3. Make sure the user list provided by stakeholders is added to the appropriate user group

4. Check the permissions of the report

3. Peer Review

Always be humble when doing a project and consider that we are human and make mistakes. Getting your colleagues to review and critique your work is the only way to achieve excellence. Ensure that the peer-review date and name of the person have been recorded in case you need to return to it.

4. UAT

Get your stakeholders involved in the testing phase of the project. They are the ones that are most familiar with the process and the data and would know if something is wrong straight away. Involving them in the Testing phase makes them feel appreciated and ensures that your project meets all their requirements. You can reflect also on the Requirements and Wireframes documents which you signed off in the initial phase of the project.