Thank you for this excellent video. One thing that does confuse me with the development process that you specified with Flows, where the Flows are *draft* until they are deployed to production, is that if the Flows are draft then the logic they contain won't be run by pre-deployment unit tests, which is surely very dangerous. If you had some unit tests that checked the state of an Account record after an account record is changed (because, say, you had some Apex Trigger logic) and you added additional on-Account-change logic via a record-triggered Flow then we want to be sure that we still get the expected Account end state, even with the additional Flow logic. But if the Flow is draft until after it is deployed to production, this surely won't be the case.
Thank you for this excellent video. One thing that does confuse me with the development process that you specified with Flows, where the Flows are *draft* until they are deployed to production, is that if the Flows are draft then the logic they contain won't be run by pre-deployment unit tests, which is surely very dangerous. If you had some unit tests that checked the state of an Account record after an account record is changed (because, say, you had some Apex Trigger logic) and you added additional on-Account-change logic via a record-triggered Flow then we want to be sure that we still get the expected Account end state, even with the additional Flow logic. But if the Flow is draft until after it is deployed to production, this surely won't be the case.