CHANGELOG.md

dbt-expectations v0.3.6

• Remove unnecessary macro to fix issue with 0.19.2 (#88)

dbt-expectations v0.3.5

Features

• Added a new macro, expect_row_values_to_have_data_for_every_n_datepart, which tests whether a model has values for every grouped date_part.

  For example, this tests whether a model has data for every day (grouped on date_col) from either a specified start_date and end_date, or for the min/max value of the specified date_col.

  tests:
      - dbt_expectations.expect_row_values_to_have_data_for_every_n_datepart:
          date_col: date_day
          date_part: day

Fixes

• Updated description of type check tests (#84 @noel)

• Fixed join syntax because Twitter induced guilt: https://twitter.com/emilyhawkins__/status/1400967270537564160

• Bump version of dbt-date to < 0.4.0 (#85)

dbt-expectations v0.3.4

Features

• Added support for optional min_value and max_value parameters to all*_between_* tests. (#70)

• Added support for strictly parameter to between tests. If set to True, striclty changes the operators >= and <= to> and <.

  For example, while

  dbt_expectations.expect_column_stdev_to_be_between:
      min_value: 0

  evaluates to >= 0,

  dbt_expectations.expect_column_stdev_to_be_between:
      min_value: 0
      strictly: True

  evaluates to > 0. (#72, #74)

Fixes

• Corrected a typo in the README (#67)

Under the hood

• Refactored get_select function to generate SQL grouping more explicitly (#63))

• Added dispatch call to expect_table_row_count_to_equal to make it easier to shim macros for the tsql-utils package (#64 Thanks @alieus!)