Hey team. Looking into some advice or insights on how to think about unit testing complex nodes in kedro (or rather nodes taking in complex data with a lot of edge cases). In these cases I usually follow the approach of integrating a lot functionality into a single node, composed of several smaller private functions.
My question: How to best test the node's actual output (standard stuff like column a shouldn't have any nulls, column b should never be lower than 10))?

• I feel like it would be impossible to create dummy data to account for all edge cases in the test function itself
• Reading from the production input table, on the other hand, defeats the purpose of unit testing.
• Does it make sense to generate synthetic or sample data from the input tables to the node and store it somewhere to be read at testing time?

Hey team,
Is it possible (or is there any workaround) to use a parameter in the catalog.yml using OmegaConfigLoader? My use case is that i want to select a parameter in Databricks Workflows and have it override a kedro param at runtime. I was trying to use a global (in globals.yml), as those can be used in the catalog.yml, but unfortunately they can not be overriden at runtime, according to the docs