Sometimes simple manual testing and smoke testing aren't enough. Are you doing production releases with hundreds of affected pages? Or are you migrating thousands of pages from one platform to another?

Automated testing provides a "go/no-go" summary. Manual testing provides an experienced view of the application's current state. What happens when you need both?

The examples are built in Azure, but you can easily use them in any cloud environment.

This talk covers scenarios and ways to build automation with manual verification steps that can stabilize tricky releases. We will work through a few known scenarios and ways I've mitigated these issues in unusual “automated” ways.