Explore the Mailosaur blog for expert insights on email & SMS testing, automation, and quality assurance
The test pyramid is a useful tool for developers and QA engineers who are getting started with testing. We provide an overview of the test pyramid and how to interpret and use it to generate useful takeaways in the context of your software project.
In this guide, we explain how you can get started with Java testing, show you where to focus your efforts for maximum impact, and provide framework recommendations for different project types.
In this guide, we take a look at what TestProject is and how you can use the testing framework to start running your own automated tests.
In this article, we cover smtp4dev, an easy-to-set-up email testing application for individual developers. We also walk through how to use smtp4dev and discuss its pros and cons.
In this article, we list four key reasons as to why you should be using an email testing service.
It’s easy to get lost in the world of JavaScript testing. That’s why we’ve put together this overview on testing for JavaScript developers. Read on to find out how to choose the best tools for your unit and E2E tests in JavaScript.
Spam filtering is a vital part of the email delivery pipeline. Still, having your carefully crafted customer email end up in the spam folder is a real bummer.
Choosing a test automation framework depends on a lot of factors and is different for every company, team and individual.
Cypress is a framework for the automated testing of browser-based applications. You can use Mailosaur to test email and SMS with Cypress.
Transactional and marketing emails are alive and well in 2021, with product teams betting big on email at a time when other communication strategies are either inefficient or simply unworkable.
Read on to learn about exploratory testing, why it’s important in Agile environments, and our take on when exploratory testing is (and is not) the right tool for you to use.
In this post, we will look at some common techniques for measuring the effectiveness of your QA team, as well as how to measure the return on investment for automation and tooling.
