VW_DATASET_TESTS

Overview

VW_DATASET_TESTS provides a comprehensive view of all test definitions in your Validatar environment — standard tests, template tests, and materialized tests. Each row represents one test version and includes its configuration, metadata links, folder hierarchy, overall result status, and quality classification.

Use this view for test inventory reporting, coverage analysis, and understanding which metadata objects are covered by which tests.

Schema

Test Identity

Test Classification

Project and Folder

Data Source Links

Metadata Links

Audit Fields

Overall Result Status

Relationships

VW_DATASET_TESTS
    │
    ├── TEST_ID → VW_DATASET_TEST_EXECUTIONS.TEST_ID (one-to-many)
    ├── TEST_PRIMARY_METADATA_LINK_OBJECT_KEY → VW_DATASET_TABLES.TABLE_KEY
    ├── TEST_PRIMARY_METADATA_LINK_OBJECT_KEY → VW_DATASET_COLUMNS.COLUMN_KEY
    ├── TEST_PRIMARY_METADATA_LINK_OBJECT_KEY → VW_DATASET_METADATA_OBJECTS.OBJECT_KEY
    ├── PROJECT_ID → VW_DATASET_JOBS.PROJECT_ID
    └── TEST_DATA_SOURCE_ID → VW_DATASET_TABLES.DATA_SOURCE_ID

Example Queries

List All Failing Tests by Quality Dimension

SELECT
    QUALITY_DIMENSION,
    SEVERITY_LEVEL,
    TEST_NAME,
    PROJECT_NAME,
    FOLDER_PATH,
    TEST_PRIMARY_METADATA_LINK_OBJECT,
    MOST_RECENT_FAILED_DATE
FROM REPOSITORY.VW_DATASET_TESTS
WHERE OVERALL_RESULT_STATUS = 'Failed'
    AND IS_ACTIVE_VERSION = TRUE
ORDER BY
    CASE SEVERITY_LEVEL
        WHEN 'Critical' THEN 1
        WHEN 'High' THEN 2
        WHEN 'Medium' THEN 3
        WHEN 'Low' THEN 4
    END,
    QUALITY_DIMENSION;

Tests Linked to a Specific Table

SELECT
    TEST_NAME,
    TEST_TYPE,
    QUALITY_DIMENSION,
    OVERALL_RESULT_STATUS,
    SEVERITY_LEVEL
FROM REPOSITORY.VW_DATASET_TESTS
WHERE TEST_PRIMARY_METADATA_LINK_OBJECT LIKE 'PUBLIC.DIM_CUSTOMER%'
    AND IS_ACTIVE_VERSION = TRUE
ORDER BY TEST_NAME;

Test Count by Type and Project

SELECT
    PROJECT_NAME,
    TEST_TYPE,
    COUNT(*) AS TEST_COUNT,
    SUM(CASE WHEN OVERALL_RESULT_STATUS = 'Passed' THEN 1 ELSE 0 END) AS PASSING,
    SUM(CASE WHEN OVERALL_RESULT_STATUS = 'Failed' THEN 1 ELSE 0 END) AS FAILING
FROM REPOSITORY.VW_DATASET_TESTS
WHERE IS_ACTIVE_VERSION = TRUE
GROUP BY PROJECT_NAME, TEST_TYPE
ORDER BY PROJECT_NAME, TEST_TYPE;

Coverage Gap: Tables with No Tests

SELECT
    t.DATA_SOURCE_NAME,
    t.FULL_PATH,
    t.TRUST_SCORE,
    t.COVERAGE_SCORE
FROM REPOSITORY.VW_DATASET_TABLES t
LEFT JOIN REPOSITORY.VW_DATASET_TESTS tst
    ON tst.TEST_PRIMARY_METADATA_LINK_OBJECT_KEY = t.TABLE_KEY
    AND tst.IS_ACTIVE_VERSION = TRUE
WHERE tst.TEST_ID IS NULL
ORDER BY t.DATA_SOURCE_NAME, t.FULL_PATH;

VW_DATASET_TEST_PROPERTIES — Extended Property Details

The companion view VW_DATASET_TEST_PROPERTIES provides a vertical (one-row-per-property) representation of detailed test attributes that don't fit cleanly into the flat VW_DATASET_TESTS structure. Each row contains a property name/value pair for a specific test version.

Schema

Property Categories

Joining Tests to Properties

Use TEST_ID as the join key. Filter to IS_ACTIVE_VERSION = TRUE for current properties.

Example: Failing Tests with a Specific Custom Field Value

Find tests in a failing state that have a custom field named "Test Tag" set to "Prioritized by Sales Team":

SELECT
    t.TEST_NAME,
    t.PROJECT_NAME,
    t.FOLDER_PATH,
    t.OVERALL_RESULT_STATUS,
    p.PROPERTY_VALUE AS TEST_TAG_VALUE
FROM REPOSITORY.VW_DATASET_TESTS t
INNER JOIN REPOSITORY.VW_DATASET_TEST_PROPERTIES p
    ON p.TEST_ID = t.TEST_ID
    AND p.IS_ACTIVE_VERSION = TRUE
WHERE t.IS_ACTIVE_VERSION = TRUE
    AND t.OVERALL_RESULT_STATUS = 'Failed'
    AND p.PROPERTY_CATEGORY = 'Custom Metadata'
    AND p.PROPERTY_NAME = 'Test Tag'
    AND p.PROPERTY_VALUE = 'Prioritized by Sales Team'
ORDER BY t.PROJECT_NAME, t.FOLDER_PATH;

Example: Tests Using Custom Calculation Success Criteria

SELECT
    t.TEST_NAME,
    t.PROJECT_NAME,
    p.PROPERTY_VALUE AS CALCULATION_EXPRESSION
FROM REPOSITORY.VW_DATASET_TESTS t
INNER JOIN REPOSITORY.VW_DATASET_TEST_PROPERTIES p
    ON p.TEST_ID = t.TEST_ID
    AND p.IS_ACTIVE_VERSION = TRUE
WHERE t.IS_ACTIVE_VERSION = TRUE
    AND p.PROPERTY_CATEGORY = 'Test Configuration Setting'
    AND p.PROPERTY_NAME = 'Record Success Criteria - Custom Calculation'
ORDER BY t.PROJECT_NAME, t.TEST_NAME;

Example: Tests Where Someone Mentioned "regression" in a Comment

SELECT DISTINCT
    t.TEST_NAME,
    t.PROJECT_NAME,
    p.PROPERTY_VALUE AS COMMENT_TEXT,
    p.MODIFIED_BY,
    p.DATE_MODIFIED
FROM REPOSITORY.VW_DATASET_TESTS t
INNER JOIN REPOSITORY.VW_DATASET_TEST_PROPERTIES p
    ON p.TEST_ID = t.TEST_ID
WHERE t.IS_ACTIVE_VERSION = TRUE
    AND p.PROPERTY_CATEGORY = 'Discussion Comment'
    AND LOWER(p.PROPERTY_VALUE) LIKE '%regression%'
ORDER BY p.DATE_MODIFIED DESC;

Example: Tests Linked to a Specific Table

SELECT
    t.TEST_NAME,
    t.PROJECT_NAME,
    p.PROPERTY_NAME AS LINK_TYPE,
    p.PROPERTY_VALUE AS LINKED_OBJECT
FROM REPOSITORY.VW_DATASET_TESTS t
INNER JOIN REPOSITORY.VW_DATASET_TEST_PROPERTIES p
    ON p.TEST_ID = t.TEST_ID
    AND p.IS_ACTIVE_VERSION = TRUE
WHERE t.IS_ACTIVE_VERSION = TRUE
    AND p.PROPERTY_CATEGORY = 'Linked Metadata Object'
    AND p.PROPERTY_VALUE LIKE '%CUSTOMER%'
ORDER BY t.PROJECT_NAME, t.TEST_NAME;

Secure View

VW_SECURE_DATASET_TEST_PROPERTIES adds USER_ID and ACCESS_TYPE columns, filtered by project membership (same security tier as VW_SECURE_DATASET_TESTS).

Databricks Notes

• The CASE expression for severity ordering works identically in both engines
• LIKE pattern matching is the same syntax
• Template tests have NULL values for overall result status columns (they don't execute directly — their materialized children do)