Redaguoti

Bendrinti naudojant

Configuration by outcome matrix sample report

  • Straipsnis

Azure DevOps Services | Azure DevOps Server 2022 | Azure DevOps Server 2020

When you've multiple configurations in your product to release, you can take a decision about releasing different configurations independently based on the progress of tests made for each configuration. An example of the configuration by outcome matrix report is shown in the following image.

Screenshot of Power BI Configuration by Outcome matrix report.

Important

Power BI integration and access to the OData feed of the Analytics Service are generally available for Azure DevOps Services and Azure DevOps Server 2020 and later versions. The sample queries provided in this article are valid only against Azure DevOps Server 2020 and later versions, and depend on v3.0-preview or later version. We encourage you to use these queries and provide us feedback.

Prerequisites

Note

This article assumes you read Overview of Sample Reports using OData Queries and have a basic understanding of Power BI.

For the report to generate useful data, the team must carry out the following activities to manage test plans:

  • Define test plans, test suites, and test cases. Specify their state. For a Test Suite to run, it must be in the In Progress state. For a Test Case to run, it must be in the Ready state. For details, see Create manual test cases.

  • Define test configurations and assign then to test cases. For details, see Test different configurations.

  • Run manual tests and verify the results. Mark the results of each validation step in the test case as passed or failed. For details, see Run manual tests.

    Note

    Testers must mark a test step with a status if it is a validation test step. The overall result for a test reflects the status of all the test steps that were marked. Therefore, the test will have a status of failed if any test step is marked as failed or not marked.

Sample queries

You can use the following queries of the TestPoints entity set to create different but similar test plan progress reports.

Note

To determine available properties for filter or report purposes, see Metadata reference for Test Plans Analytics. You can filter your queries or return properties using any of the Property values under an EntityType or NavigationPropertyBinding Path values available with an EntitySet. Each EntitySet corresponds to an EntityType. For more information about the data type of each value, review the metadata provided for the corresponding EntityType.

Copy and paste the following Power BI query directly into the Get Data > Blank Query window. For more information, see Overview of sample reports using OData queries.

let 
    Source = OData.Feed ("https://analytics.dev.azure.com/{organization}/{project}/_odata/v3.0-preview/TestPoints?" 
        &"$apply=filter((TestSuite/TestPlanTitle eq '{testPlanTitle}'))" 
        &"/groupby((TestConfiguration/Name, LastResultOutcome)," 
            &"aggregate($count as Count)" 
        &")", null, [Implementation="2.0"]) 
in 
    Source

Substitution strings and query breakdown

Substitute the following strings with your values. Don't include brackets {} with your substitution. For example if your organization name is "Fabrikam", replace {organization} with Fabrikam, not {Fabrikam}.

  • {organization} - Your organization name
  • {project} - Your team project name, or omit "/{project}" entirely, for a cross-project query
  • {testPlanTitle} - Title of your test plan. Example: Fabrikam test plan.

Query breakdown

The following table describes each part of the query.

Query part

Description

filter((TestSuite/TestPlanTitle eq '{testPlanTitle}'))

Return data for only selected test plan. You can add multiple plans with a clause like filter((TestSuite/TestPlanTitle eq '{testPlanTitle1}' or TestSuite/TestPlanTitle eq '{testPlanTitle2}')). You can also apply any other filters related to test suites, test configurations here.

/groupby((TestConfiguration/Name, LastResultOutcome),

Grouping the points by the test configuration names and their outcome.

/aggregate($count as Count)

Aggregate data across the filtered test points with having count as Count.

(Optional) Rename query

You can rename the default query label, Query1, to something more meaningful. Simply enter a new name from the Query Settings pane.

Screenshot of Power BI query menu options, rename query.

Expand the TestConfiguration column

  1. Expand TestConfiguration

    • Choose the expand button.

      Power BI Expand Test configuration

    • Select the fields to flatten.

      Power BI select fields to flatten

    • The table now contains entity field of TestConfiguration.Name.

      Power BI expanded test configuration

  2. (Optional) Right-click a column header and select Rename...

    Screenshot of Power BI transform data, Rename Columns.

Change the data type of select columns

From the Power Query Editor, select the columns containing a number, such as Blocked, Failed, and NotApplicable; select Data Type from the Transform menu; and then choose Whole Number. For more information about changing the data type, see Transform Analytics data to generate Power BI reports, Transform a column data type.

Close the query and apply your changes

Once you've completed all your data transformations, choose Close & Apply from the Home menu to save the query and return to the Report tab in Power BI.

Screenshot of Power Query Editor Close and Apply option.

Create the Matrix report

  1. Under Visualizations, choose Matrix.
  2. Add TestConfiguration.Name to Rows.
  3. Add LastResultOutcome to Columns.
  4. Add Count to Values.
  5. Select Sum as aggregation for Count.

    Screenshot of Power BI select Sum as aggregation.

Your report should look similar to the following image.

Screenshot of Power BI Sample Configuration by Outcome matrix report.