The proper solution to tests sharing state would be randomization. Unless we are locked to real hardware - even then there is virtualization - we can randomize anything. We saw an example of this in the blog post about email testing , under the section Achieving Stateless tests with unique emails. With mailosaur any-name@unique-serverId.mailosaur.io went to that unique email server inbox, and we differentiated... - Source: dev.to / over 2 years ago

There are plenty of email testing solutions available, and combinations of test frameworks that integrate with them. For the code snippets and working examples, we will be using Cypress and Mailosaur, but the ideas should generally apply to any tuple of email services and test automation frameworks. - Source: dev.to / over 2 years ago

Somewhat related anecdote. Whilst we didn't get cut off, we found a huge drop-off in time to receive, and the quality of, support from our live chat/support messaging provider. Having been a customer since our launch [1], and very early after theirs, it has been really sad and frustrating to see that friendly distrupter energy zap out of the service. I get why businesses go through that changes like this during... - Source: Hacker News / about 3 years ago

We have enjoyed using mailosaur. Also makes it easy to see cc, bccs, etc at a glance. Source: over 3 years ago

Before we talk about build & deployment, let's get this straight: We are using Azure DevOps online offering. However this could as well be On-Premises installation or any other CI/CD platform of your choice. We are, however, using self-hosted agents that perform the build tasks. - Source: dev.to / over 2 years ago

Azure DevOps Server | Microsoft Azure. Source: almost 3 years ago