Testing applications behind a login flow is cumbersome. And it gets even worse when there’s two-factor authentication (2FA) involved. Many people work around this problem by disabling it or implementing wild hacks. Automating a 2FA-based login flow is just too hard! I thought that for a long time, too. But I must admit — I was wrong.

If you’ve worked with load testing before, you know that there are a lot of things to consider. Whether or not you should combine load testing and mocks is one of those considerations. Getting to the answer requires knowledge of your infrastructure and your development procedures, which will all influence what questions you need to ask yourself.

Traditional software application infrastructure generally followed a monolithic pattern; one application connected to one database. Understanding what was going on inside the application itself was a simple proposition, with relevant logs and metrics all originating from the same source. When it came time to scale, the answer was to get a bigger server or to get more servers.

You’ve forgotten to add frontend validation to number fields, and now people are getting an error when they enter text into those fields. However, this is an issue that’s easily preventable—by implementing a proper test that checks for edge cases, but how do get started with software testing? Avoiding bugs in production is just one advantage of testing, it also helps you be more confident about your applications, opens up the potential for a full CI/CD pipeline, and much more.

“Testing your production environment” refers to the practice of running tests on production servers, using actual data from real users. Production testing doesn’t replace other methods like unit or integration testing. Instead, it extends them. Smoke testing is one approach that Lumigo has implemented to test our own production environments.

Components are reusable bits of code that, most of the time, work and function independently. If you want to be confident that components are working properly, you need to test them. Conveniently, Cypress.io has designed their testing framework to include component testing. This tutorial illustrates the differences between end-to-end (E2E) and component testing, and what to consider when using these methods. Then, you will learn how to use Cypress for component testing.

Today Codecov is joining the Sentry family. Codecov began as a code coverage reporting tool in 2014 and has since emerged as a market leader in the test analytics space. Codecov makes coverage actionable for over two dozen test frameworks, and has helped over a million software developers improve their approach to testing, coverage, and code reliability. You might be asking, what do test analytics have to do with application monitoring?