Elementary Community

image.png

A question regarding `test_result_rows`

I have not altered any default settings for this at all. Yet I have one test in the report showing the rows (with all associated columns), and another which does not. See image for the two tests

*Why is this happening?* The only difference I can see in my test is that one test uses `dbt_utils` and one does not. Test yaml in the thread.

```  - name: fct_dyn_bookings_and_active_reservations
    config:
      elementary:
        timestamp_column: createdon
    columns:
      - name: total_agreed_value_gbp
        tests:
          - not_null
      - name: lease_length_weeks
        tests:
          - dbt_utils.accepted_range:
              min_value: 0
              inclusive: true
              config:
                severity: warn```


I think this makes sense now I've seen the underlying test sql, one test does a select *, the other one only selects the affected column.

I needed to set `store_failures: true` for the dbt native test. Just happened that the dbt_utils test I had happened to return all columns by default.