// TODO

LOL. What did this comment (no pun!) do for your HN karma points?

That would be an integration test, not a unit test.

That is probably quite straight forward and of course they have 100% coverage.

Checksum on the resulting csv with a parallel implementation of the whole pipeline ;)

I don’t work with large databases so pardon my ignorance. Is there typically a “unit test” bucket you run it on or do you just put in test entries on a production bucket?

Normally you'd fire up a separate environment, mock the process and see if it produces the expected results. By the time you put 'test entries in a production bucket' there are so many lines crossed that it likely won't end well even if the tests do pass.

We tend to only test what is being tested. So, most DB calls are mocked in our unit tests. For stored procs or other tests that need to be run on a DB, we use a test DB that is setup to mirror production.

I'd bet there are a 100 different answers to your question though. This is the way we handle it.

We usually use very complicated UIPath flows to “test” these things.

If that doesn’t exist yet (it usually doesn’t), we test manually, but only core workflows.