This website uses cookies to ensure you get the best experience.
Learn more.
A transformation library should be tested without rerunning the complete production workflow. What design best enables this?
Published
- Test only that the notebook's title is present
- Separate transformation functions and test DataFrame outputs and schemas
- Place all code in one interactive cell with production credentials
- Remove schema assertions because rows were counted
Comments — 0
Sign in to comment