David Leslie

If you were to plug the question, "What does QA mean?" into your favorite search tool, you would get about 7,980,000 results. However, we need to define what Q.A. is an acronym for before we can start talking about the true definition of it. I want to take a step back to reset our foundation when we talk about QA. So let’s get into it; what does QA really mean?

A strange, uneasy feeling came over me while I chatted with a project manager about an upcoming ecommerce project. As we talked about the project's goals, expectations from the team, the timeline, and the challenges the project team will face, the stranger I started to feel. Looking at the chicken scratches on my iPad, which passed as my notes, the source of the unease jumped out in three bullet points: Agile, Automation, and AI. These three elements can make or break your project.

Like the Headless Horseman, the frontend and backend are decoupled in headless ecommerce. This means that testers no longer have to wait for both the frontend and the backend to be completed before they start testing. But this also means that they have to, in a sense, test the same feature three different times. So how do you do this?

Just because your application has moved to the cloud doesn't mean all the best practices you’ve built up go away. Instead, look at your cloud environment as something that buys you both time and flexibility that you still have to test.

Testing APIs used in the MACH framework is essential to ensure that they are reliable, efficient, and secure. By following the best practices outlined here, you can certify that your APIs are able to handle the demands of a busy ecommerce environment.

As the M in the MACH framework acronym, understanding the role that Microservices play is critical to understanding how to test them during development as well as during End-to-End testing. Think of microservices like individual Lego bricks that, on their own, don’t do much. But, when they are combined, they can build anything.