Draft automation is what the maker is still changing. Published automation is what customers and app users can reach. Keep the two separate in your testing.
Use draft testing while building:
Change the setup.
Run validation.
Create a test request.
Preview as each role.
Fix issues.
Repeat.
Draft testing is allowed to be messy because it is not public yet.
Published testing should be boring and predictable. After publishing, run a clean test with a new record and a real role. Confirm that published users can start the workflow, see the destination, act on the item, and see the result.
A maker tests in draft, publishes, and assumes the published app is identical. Always verify the published app if permissions, roles, screen navigation, or custom domains are involved.
Make changes in draft.
Validate.
Test with roles.
Publish.
Test the published app.
Keep the test record or screenshot as proof for customer handoff.
