Tests with auto stubs: how to choose a technology, set up a process and not get to hell

Only the lazy person will now deploy the product into production without any tests or manual checks. 

However, what is the way to make stable releases several times a week with many merge requests when you don't have a fully prepared integration infrastructure, and it's impossible to have it? 

Someone will say docker containers can help you. But what exactly is it, and is it really good? 

I want to show you how our product team has achieved frequent painless releases. 

How we combined docker containers, the divine model, static analysis of test code, and dynamic stubs of third-party services in our approach to making tests. 

Listeners will get a checklist to make tests with auto stubs.