Send us a text

This week we discuss an often neglected part of many BI implementations: testing.  It isn't glamorous, it isn't the headline-grabbing side of a project, but it is vital.  After all, what use is a report if it doesn't show the right information.

We talk about different approaches to testing, from structured tests following a script to unstructured exploratory testing.  We discuss why both are important elements of a rounded test plan, and why it should never simply be left to the developers to test their own reports.  And to be clear - we are not suggesting development teams would cynically pass on reports they know to be broken, but rather that when you have been working on piece of code for weeks, it's hard to see where errors might be creeping in.

Finally, we talk about non-functional testing.  This is probably the most neglected part of an already neglected process.  It is vital that a report performs well, has readable fonts and suitable colours.  If any of these aren't the case, the report consumers will quickly be turned off and revert to other ways of reporting data.

You can download Power BI Desktop from here.

If you already use Power BI, or are considering it, we strongly recommend you join your local Power BI user group here.

To find out more about our services and the help we can offer, contact us at one of the websites below:
UK and Europe: https://www.clearlycloudy.co.uk/
North America: https://clearlysolutions.net/