Post #2951167
2023-08-09 06:30 UTC
@djnavarro@fosstodon.org @milesmcbain@fosstodon.org
Exactly that‘s my question after reading the tutorial. When using assertion and when tests?
My feeling is that easy within dataframe tests can be done with assert, but more complex analysis with tests, think of: does my join result in a certain expected number of rows?
Where do you draw the line?
Replies (1)
-
@milesmcbain@fosstodon.org 2023-08-09 10:39
@cutterkom@mastodon.social @djnavarro@fosstodon.org Excellent question. I had some related thoughts: https://www.milesmcbain.com/posts/assertive-programming-for-pipelines/ The gist being you're better off doing assertive programming because that ensures every pipeline run adheres to yours assertions. But there's still a related question which is: Do I want to fail fast as soon as any assertion fails? or do I want to check all my assertions and record data about each failure? I use both strategies at different times.