Can I get check list of what to test in Power BI report?

Question

I am currently working on a project where after the ETL process, Power BI reports are generated. How do I test those report? What to test in generated reprots? I have access to DB and .pbix file as well.

Answer 1

Here's How I tested the reports once

1. Write your own query based on requirements and match data for few records and counts of few columns and total count of records in reports

2. Modify the data so that and generate the report again, verify the updated data is shown in reports. Modify is insert, update and delete data.

Comments

Thank Jitendra. I will try your suggestions.

---

Do you have any test case template sample for this?

Answer 2

Here is my checklist:

• Make sure that .pbix file points to appropriate data source.
• Whether report pointing to new universe name
• When Data Providers are linked, check whether they are linked to common dimensions.
• Correct use of Results / Condition Objects (For example, for result objects ensure any redundant objects are removed, or for condition objects if a filter object is available a dimension object is not used)
• Correct use of operator in the condition object
• All query build are relevant to report requirements
• Select appropriate Template for proper Report (where applicable)
• Make sure that reports has proper layout. It works on windows and mac. When loaded with more data, it should not break the page.
• Make sure that report font, colour, style are set as expected and are same across all reports.
• Make sure that unused variable and formulas are removed from the report
• Make sure that all required conditions or filters work fine.
• If formulas used, make sure that Zero Divide error is handled
• If alerts or breaks are used, make sure those are set properly.
• Make sure that sections are created on the right object.
• Reports should have meaningful user variable names.
• Make sure that two tables do not overlap.
• In table make sure that we have minimal horizontal or vertical rows
• Make sure that table, cross table or chart formats are followed as per requirements
• If the report is drillable, make sure that drilling down works fine.
  • Verification of the layout format per the design mock-up, style sheets, prompts and filters attributes and metrics on the report.
  • Verification of drilling, sorting and export functions of the reports in the Web environment.
  • Verification of reports containing derived metrics (Special focus should be paid to any subtotals or aggregates)
  • Reports with "non-aggregate-able" metrics (e.g., inventory at hand) also need special attention to the subtotal row. It should not, for example, add up the inventory for each week and show the inventory of the month.
  • The test team should target the lowest granularity that is present in the data warehouse if it is higher than the transaction grain at the OLTP.
  • Understand each report & the linkages of every field displayed in the report with the star schema and trace its origin back to the source System.
• Tabs name should be meaningful and it should describe about the data.
• Testing multiple time with different set of data such as different regions over different time period.
• System should NOT allow the user to upload .rar data files
• Proper permission and access to data should be tested.
• Make sure that generated views are not out of date.
• Make sure aggregate data and derived data are not easily tied back to a source.