Yes, but with an important nuance. Elementary does store result samples for passing tests in

test_result_rows

in general. This is intentional so that samples can be shown in the report and alerts, and it’s the expected behavior for successful tests as well. [[Slack – store samples](https://elementary-community.slack.com/archives/C02CTC89LAX/p1685719941706139)] However, other sources state that

test_result_rows

contains only samples of failed rows, and that only failures are stored. [[Package models – test_result_rows](https://docs.elementary-data.com/dbt/package-models#run-results); [Slack – failing rows sample](https://elementary-community.slack.com/archives/C02CTC89LAX/p1709061533176029)] Because of this contradiction, I can’t say with certainty what behavior your current version has. If in your environment passing tests do not create rows in

test_result_rows

, there isn’t a documented configuration in the provided sources that forces storage of samples specifically for passing tests. If you need visibility into passing tests: - Use

elementary_test_results

, which always records all dbt tests (pass and fail) with their metadata and status. [[Package models – elementary_test_results](https://docs.elementary-data.com/dbt/package-models#run-results)] - If you need full row-level data for passes as well, the only documented option is to rely on dbt’s native

store_failures

feature per test, and then build your own combined view from those tables; Elementary doesn’t add another mechanism for storing all passing rows. [[Slack – store_failures suggestion](https://elementary-community.slack.com/archives/C02CTC89LAX/p1686303135355179)] So, based on the available docs: there is no clearly documented way to guarantee row samples for passing tests in

test_result_rows

if they are not appearing there today.