Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions dbt-athena/.changes/unreleased/Fixes-20251115-223739.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
kind: Fixes
body: Add integration test documentation to CONTRIBUTING.md
time: 2025-11-15T22:37:39.7261048+08:00
custom:
Author: godhahn
Issue: "843"
34 changes: 33 additions & 1 deletion dbt-athena/CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,36 @@
# Contributing to `dbt-adapters`
# Contributing to `dbt-athena`

This document covers the incremental content beyond what is contained in the repository's [CONTRIBUTING.md](/CONTRIBUTING.md).
You are strongly encouraged to start there first if you are reading this for the first time.

# Testing

## 1. Configure Environment

From the `dbt-athena` directory, run `hatch run setup` to create a `test.env` file. Populate this file with your Athena connection details.

* `DBT_TEST_ATHENA_S3_STAGING_DIR`
* `DBT_TEST_ATHENA_S3_TMP_TABLE_DIR`
* `DBT_TEST_ATHENA_REGION_NAME`
* `DBT_TEST_ATHENA_DATABASE`
* `DBT_TEST_ATHENA_SCHEMA`
* `DBT_TEST_ATHENA_WORK_GROUP`
* `DBT_TEST_ATHENA_THREADS`
* `DBT_TEST_ATHENA_POLL_INTERVAL`
* `DBT_TEST_ATHENA_NUM_RETRIES`
* `DBT_TEST_ATHENA_AWS_PROFILE_NAME`

## 2. Run Tests

Once `test.env` is configured, you can run tests using `hatch`:

```shell
# run all integration tests
$ hatch run integration-tests

# run tests for a specific module
$ hatch run integration-tests tests/functional/adapter/test_basic_hive.py

# run a specific test class
$ hatch run integration-tests tests/functional/adapter/test_basic_hive.py::TestSimpleMaterializationsHive
```
6 changes: 6 additions & 0 deletions dbt-bigquery/.changes/unreleased/Fixes-20251115-223927.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
kind: Fixes
body: Add integration test documentation to CONTRIBUTING.md
time: 2025-11-15T22:39:27.7160737+08:00
custom:
Author: godhahn
Issue: "843"
31 changes: 31 additions & 0 deletions dbt-bigquery/CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,3 +2,34 @@

This document covers the incremental content beyond what is contained in the repository's [CONTRIBUTING.md](/CONTRIBUTING.md).
You are strongly encouraged to start there first if you are reading this for the first time.

# Testing

## 1. Configure Environment

From the `dbt-bigquery` directory, run `hatch run setup` to create a `test.env` file. Populate this file with your BigQuery connection details.

* `BIGQUERY_TEST_NO_ACCESS_DATABASE`
* `BIGQUERY_TEST_SERVICE_ACCOUNT_JSON`
* `BIGQUERY_TEST_ICEBERG_BUCKET`
* `DBT_TEST_USER_1`
* `DBT_TEST_USER_2`
* `DBT_TEST_USER_3`
* `COMPUTE_REGION`
* `DATAPROC_CLUSTER_NAME`
* `GCS_BUCKET`

## 2. Run Tests

Once `test.env` is configured, you can run tests using `hatch`:

```shell
# run all integration tests
$ hatch run integration-tests

# run tests for a specific module
$ hatch run integration-tests tests/functional/adapter/test_basic.py

# run a specific test class
$ hatch run integration-tests tests/functional/adapter/test_basic.py::TestSimpleMaterializationsBigQuery
```
6 changes: 6 additions & 0 deletions dbt-postgres/.changes/unreleased/Fixes-20251115-223906.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
kind: Fixes
body: Add integration test documentation to CONTRIBUTING.md
time: 2025-11-15T22:39:06.7814256+08:00
custom:
Author: godhahn
Issue: "843"
31 changes: 31 additions & 0 deletions dbt-postgres/CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,3 +2,34 @@

This document covers the incremental content beyond what is contained in the repository's [CONTRIBUTING.md](/CONTRIBUTING.md).
You are strongly encouraged to start there first if you are reading this for the first time.

# Testing

## 1. Configure Environment

From the `dbt-postgres` directory, run `hatch run setup` to create a `test.env` file. Populate this file with your Postgres connection details.

* `POSTGRES_TEST_HOST`
* `POSTGRES_TEST_PORT`
* `POSTGRES_TEST_USER`
* `POSTGRES_TEST_PASS`
* `POSTGRES_TEST_DATABASE`
* `POSTGRES_TEST_THREADS`
* `DBT_TEST_USER_1`
* `DBT_TEST_USER_2`
* `DBT_TEST_USER_3`

## 2. Run Tests

Once `test.env` is configured, you can run tests using `hatch`:

```shell
# run all integration tests
$ hatch run integration-tests

# run tests for a specific module
$ hatch run integration-tests tests/functional/adapter/test_basic.py

# run a specific test class
$ hatch run integration-tests tests/functional/adapter/test_basic.py::TestSimpleMaterializations
```
6 changes: 6 additions & 0 deletions dbt-redshift/.changes/unreleased/Fixes-20251115-223819.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
kind: Fixes
body: Add integration test documentation to CONTRIBUTING.md
time: 2025-11-15T22:38:19.2782804+08:00
custom:
Author: godhahn
Issue: "843"
36 changes: 36 additions & 0 deletions dbt-redshift/CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,3 +2,39 @@

This document covers the incremental content beyond what is contained in the repository's [CONTRIBUTING.md](/CONTRIBUTING.md).
You are strongly encouraged to start there first if you are reading this for the first time.

# Testing

## 1. Configure Environment

From the `dbt-redshift` directory, run `hatch run setup` to create a `test.env` file. Populate this file with your Redshift connection details.

* `REDSHIFT_TEST_HOST`
* `REDSHIFT_TEST_PORT`
* `REDSHIFT_TEST_DBNAME`
* `REDSHIFT_TEST_USER`
* `REDSHIFT_TEST_PASS`
* `REDSHIFT_TEST_REGION`
* `REDSHIFT_TEST_CLUSTER_ID`
* `REDSHIFT_TEST_IAM_USER_PROFILE`
* `REDSHIFT_TEST_IAM_USER_ACCESS_KEY_ID`
* `REDSHIFT_TEST_IAM_USER_SECRET_ACCESS_KEY`
* `REDSHIFT_TEST_IAM_ROLE_PROFILE`
* `DBT_TEST_USER_1`
* `DBT_TEST_USER_2`
* `DBT_TEST_USER_3`

## 2. Run Tests

Once `test.env` is configured, you can run tests using `hatch`:

```shell
# run all integration tests
$ hatch run integration-tests

# run tests for a specific module
$ hatch run integration-tests tests/functional/adapter/test_basic.py

# run a specific test class
$ hatch run integration-tests tests/functional/adapter/test_basic.py::TestSimpleMaterializationsRedshift
```
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
kind: Fixes
body: Add integration test documentation to CONTRIBUTING.md
time: 2025-11-15T22:38:46.9746906+08:00
custom:
Author: godhahn
Issue: "843"
37 changes: 37 additions & 0 deletions dbt-snowflake/CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,3 +2,40 @@

This document covers the incremental content beyond what is contained in the repository's [CONTRIBUTING.md](/CONTRIBUTING.md).
You are strongly encouraged to start there first if you are reading this for the first time.

# Testing

## 1. Configure Environment

From the `dbt-snowflake` directory, run `hatch run setup` to create a `test.env` file. Populate this file with your Snowflake connection details.

* `SNOWFLAKE_TEST_ACCOUNT`
* `SNOWFLAKE_TEST_ALT_DATABASE`
* `SNOWFLAKE_TEST_ALT_WAREHOUSE`
* `SNOWFLAKE_TEST_DATABASE`
* `SNOWFLAKE_TEST_OAUTH_CLIENT_ID`
* `SNOWFLAKE_TEST_OAUTH_CLIENT_SECRET`
* `SNOWFLAKE_TEST_OAUTH_REFRESH_TOKEN`
* `SNOWFLAKE_TEST_PASSWORD`
* `SNOWFLAKE_TEST_QUOTED_DATABASE`
* `SNOWFLAKE_TEST_USER`
* `SNOWFLAKE_TEST_WAREHOUSE`
* `SNOWFLAKE_TEST_CATALOG_LINKED_DATABASE`
* `DBT_TEST_USER_1`
* `DBT_TEST_USER_2`
* `DBT_TEST_USER_3`

## 2. Run Tests

Once `test.env` is configured, you can run tests using `hatch`:

```shell
# run all integration tests
$ hatch run integration-tests

# run tests for a specific module
$ hatch run integration-tests tests/functional/adapter/test_basic.py

# run a specific test class
$ hatch run integration-tests tests/functional/adapter/test_basic.py::TestSimpleMaterializationsSnowflake
```
Loading