Untitled

    The probes queried from datasources come back in different formats depending on the datasource technology, the query-language used and also the driver. A result from an MDX query for example adds many more columns with metadata that you didn't query explicitly. And also REST-API's return deep structures of data that are not comparable to table-shaped data.

    The test-engine of BiG EVAL unifies query results so they get comparable to each other. This is called extraction. You just need to tell BiG EVAL which extraction method to apply to the query result. And possible some parameters.

    You can find the extraction-settings in configuration-interface of every probe. Open a testcase in the testcase-editor and switch to the tab "probes".

    extractions_de.png

     

    The following extraction-methods are available

     

     

    Extraction of single values

    Use one of the following extraction-methods to extract scalar single-values like a KPI-value, the result of a function (sum, count ...) from a query result and use it as the probe value.

    Example of a scalar single-value
    scalar_value.png

    The following example of a testcase shows a possible usage scenario of a scalar single-value. In this example a single-value probe gets taken from the ERP- and also from the DWH-system.

    scalar_value_usage_sample_01.png

     

    Values of the first cell

    Extracts the value of the first cell and the first row and uses it as a scalar single-value.

    first_cell.png

    or

    first_cell_01.png

     

    Value of a specific cell

    Extracts the value of a specific cell of the first row and uses it as a scalar single-value. To specify the column whos value should be taken, you need to enter the column-name or -position (zero based) into the "Columns" field.

    specific_cell.png

     

     

    Extraction of multiple values

    To extract multiple scalar single-values from a query result, you can use the following extraction-methods. They allow to query multiple values like KPI-values or function-results (Sum, Count ...) in one single probe.

    Example of a multi-value probe:

    multi_cells.png

    The following example shows you how to use multi-value probes in a testcase. In this example we take multiple values like Revenue and COGS from the ERP and also from the DWH. Each of them as a multi-value probe. Afterwards they get compared to each other.

    multi_cells_usage_sample_01.png

     

    Values of multiple cells

    Extracts the values of multiple cells of the first row of the query result as the probe value.

    specific_cells.png

    Specify the columns to use by entering the column-names or -positions (zero-based) separated by a semicolon ; into the "columns" field.

    Revenue;COGS

     

    Values of the first row

    BiG EVAL uses the full first row of the query result as the probe value.

    first_row.png

     

    Tabular extraction

    To use whole tables with one or more columns and multiple rows as a probe value you can use the following extraction-mehtods. You can use this to compare smaller or even large tables, to compare matrices or grouped KPI-values.

    Exaple of a tabular probe:

    table.png

    The following usage example shows you how two tabular probe values could be used in a comparison. One table comes out of the ERP and the other from the data warehouse.

    table_usage_sample_01.png

     

    Values of specific columns

    Extracts the values of multiple columns and all rows of the query result. The result is a table with one or multiple columns and as many rows as the datasource query returned.

    specific_columns.png

    Specify the columns to use by entering the column-names or -positions (zero-based) separated by a semicolon ; into the "columns" field.

    ProductID;COGS

    Specify the columns to use as the key that identifies each row by entering the column-names or -positions (zero-based) separated by a semicolon ; into the "key-columns" field.

     

    Whole Table

    BiG EVAL uses the whole datasource query result as the probe value.

    whole_table.png

    Specify the columns to use as the key that identifies each row by entering the column-names or -positions (zero-based) separated by a semicolon ; into the "key-columns" field.

    ProductID

     

     

     

    Was this article helpful?
    0 out of 0 found this helpful

    Comments