Why Don't Data Engineers Write Tests?
Why Don't Data Engineers Write Tests?
I asked this same question last week in the r/dataengineering subreddit and got some interesting answers: - Unit/Integration testing is often dropped because of tight deadlines and low perceived business impact. - It helps, but they're not a full solution for data quality. - Many Data Engineers don't have a Software Engineering background, so common practices like testing often aren't applied. - Creating multiple input/output tables with realistic synthetic data is complicated. - Tooling and frameworks for testing data transformations are still pretty limited. I'd like to hear Hacker News's perspective on this. I also built an open-source toolkit/framework called Pybujia to help with some of these pains: https://github.com/jpgerek/pybujia/
Share cardActual performance
Launch Intel predictions
Analyze your own launch →Incorrect prediction on native model
Similar products
Python Tests That Write Themselves
CrashBreak – Reproduce exceptions as failing tests in Ruby
PANIC – Distributed Jepsen Tests for Everyone
Module for conditionally skipping Mocha tests
Documentaion Tests with Vitest
Unicorn reporter for AngularJS tests
Mocha tests from Vim
Bluefin – Groovy DSL for Selenium tests
Find empty tests in your suites
Use realistic tests to hire engineers