boundary

Commit Graph

Author	SHA1	Message	Date
Timothy Messier	c8bf1917f5	db: Refactor test setup for pre-populated data Now when initializing the test database for sql tests, it will load the colors persona data into the database. This will provide a data set that tests can use without needing to call `wtt_load`. The main motivation is to allow for a separation of setup and test execution that requires crossing a transaction boundary. The pgTap tests are required to exectue as a single transaction, so that the rollback can reset the state, and each test can be isolated. However, can cause issues with some test senarios, particuarly with the use of some times releated functions like `current_timestamp` and `now` which return the time that the current transaction started. This creates an issue if a test relies on some setup that sets a time via `now`, then an update that expects a new time via `now`. See: https://www.postgresql.org/docs/13/functions-datetime.html#FUNCTIONS-DATETIME-CURRENT	5 years ago
Timothy Messier	624bdbf0c2	test(db): Add baseline tests for wh_user_dimension (#1454 ) This sets up the configuration for running a new suite of tests that are written in sql, to test the sql logic implemented in plpgsql functions and triggers. It is primarily designed to provides tests for the data warehouse functionality that is implemented purely in sql. The infrastructure to run these tests leverages docker. It creates one docker container using the `library/postgres` image and provisions the database with the boundary sql migrations and test helper functions. A separate docker container is run that has the pgtap extension and pg_prove cli to execute the tests. As noted, pgtap is used for the tests. This postgresql extension provides a number of helpful assertion functions to make writing sql tests easier. It also, along with the pg_prove cli, provides readable test output. Along with the new testing infrastructure this commit establishes a baseline of tests for the wh_user_dimension: - Unit tests for individual views and functions: - whx_user_dimension_source - whx_user_dimension_target - wh_upsert_user - Integration tests for that verify that the wh_user_dimension gets populated correctly when sessions are inserted or updated. This ensures that: - the trigger runs on session insert - the trigger results in the correct changes to the wh_user_dimension. This commit provides a `Makefile` to run the tests locally that provides support for: - Setting the postgres docker image to easily test multiple versions. - Passing through options to pg_prove - Passing the test list to run individual tests - Additional targets to separately startup the database image to quickly re-run tests while developing new tests. Lastly configures circleci to run this test suite as a matrix build in parallel with the other tests. The matrix build tests multiple versions of postgres: - latest - 13-alpine - 12-alpine - 11-alpine See: https://pgtap.org/	5 years ago

Author

SHA1

Message

Date

Timothy Messier

c8bf1917f5

db: Refactor test setup for pre-populated data

Now when initializing the test database for sql tests,
it will load the colors persona data into the database. This will
provide a data set that tests can use without needing to call
`wtt_load`.

The main motivation is to allow for a separation of setup and test
execution that requires crossing a transaction boundary. The pgTap tests
are required to exectue as a single transaction, so that the rollback
can reset the state, and each test can be isolated. However, can cause
issues with some test senarios, particuarly with the use of some times
releated functions like `current_timestamp` and `now` which return the
time that the current transaction started. This creates an issue if a
test relies on some setup that sets a time via `now`, then an update
that expects a new time via `now`.

See: https://www.postgresql.org/docs/13/functions-datetime.html#FUNCTIONS-DATETIME-CURRENT

Timothy Messier

624bdbf0c2

test(db): Add baseline tests for wh_user_dimension (#1454 )

This sets up the configuration for running a new suite of tests that are
written in sql, to test the sql logic implemented in plpgsql functions
and triggers. It is primarily designed to provides tests for the data
warehouse functionality that is implemented purely in sql.

The infrastructure to run these tests leverages docker. It creates one
docker container using the `library/postgres` image and provisions the
database with the boundary sql migrations and test helper functions.  A
separate docker container is run that has the pgtap extension and
pg_prove cli to execute the tests.

As noted, pgtap is used for the tests. This postgresql extension
provides a number of helpful assertion functions to make writing sql
tests easier. It also, along with the pg_prove cli, provides readable
test output.

Along with the new testing infrastructure this commit establishes a
baseline of tests for the wh_user_dimension:

- Unit tests for individual views and functions:
    - whx_user_dimension_source
    - whx_user_dimension_target
    - wh_upsert_user
- Integration tests for that verify that the wh_user_dimension gets
  populated correctly when sessions are inserted or updated. This
  ensures that:
    - the trigger runs on session insert
    - the trigger results in the correct changes to the
      wh_user_dimension.

This commit provides a `Makefile` to run the tests locally that provides
support for:

- Setting the postgres docker image to easily test multiple versions.
- Passing through options to pg_prove
- Passing the test list to run individual tests
- Additional targets to separately startup the database image to quickly
  re-run tests while developing new tests.

Lastly configures circleci to run this test suite as a matrix build
in parallel with the other tests. The matrix build tests multiple
versions of postgres:

- latest
- 13-alpine
- 12-alpine
- 11-alpine

See:
    https://pgtap.org/

2 Commits (c8bf1917f5f40e4e28cff2149c01d9cd55966f2e)