How are teams testing declarative pipeline changes before promoting to production?
Our pipeline definitions are moving toward a declarative model, but our current tests mostly validate notebooks in isolation. I would like a promotion workflow that catches schema drift, expectation failures, and unintended full refreshes before a production run. What does a practical test environment and release gate look…