DataEngBytes 2023 PER-T1-10 - Matthew Carter
summary
CICD pipelines run automated checks that catch surprises before users see them: merge to GitHub triggers GitHub Actions (or CircleCI/Codefresh) which deploys to a test environment, runs end-to-end tests with pytest and gherkin to catch logic flips (example: a transform suddenly reporting $1,000,000 profit vs negative cash), runs RBAC checks against Snowflake via parameterized pytest to block privilege escalations, and runs data quality checks with Soda or DBT contracts (types, nulls, freshness); alerting goes to Slack/Teams and tests must be designed to fail noisily and finish quickly.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:03CI/CD explained
- 2:48End-to-end testing
- 8:06Security testing
- 11:36Data quality testing
- 14:46Why testing matters
- 16:53Alerting strategies
- 19:20Summary
related talks
41mDataEngBytes 2023 - BRI-T1-01 - Chad Sanderson
28mDataEngBytes 2023 - SYD-T1-03 - Chad Sanderson
24mDataEngBytes 2023 - MEL-T2-02 - Vikas Rajput
29mDataEngBytes 2023 - SYD-T1-08 - Rishu Saxena & John Cosgrove
21mDataEngBytes 2023 - SYD-T3-04 - Abhinav Goyal
32mDataEngBytes 2023 - BRI-T1-10 Rishu Saxena & John Cosgrove
19mRobust CI Workflow with dbt for Data Warehouse Optimization
22mData Integrity Tests in CI/CD Pipelines
