Every product is made of multiple layers of computer systems that need to transfer data from point A to point B. Sometimes that information is transferred inside your team, sometimes outside your team, and sometimes outside the company. Sure, teams will need to follow least privilege practices at each step of the process but let’s spend a moment to discuss what we can do with the data and how we test it’s various states.

With different vantage points for "quality" how do you show success? Are teams spending hours running manual tests instead of relying on automated coverage the could be built out? Were there other testing considerations from a technology standpoint that might help add the right test coverage in areas with higher value? How many emergency meetings arise when a customer was unable to use the product as they expected? Creating the correct testing strategy that it's confusing to begin with.

Hi! My name is Jessica and I'm a Full Stack Quality Engineer. If you've ever worked in software you've spent a lot of time thinking about the quality of your deliverables. Most of us have laughed. Or cried very much depending on the day. But regardless this topic resonates with anyone working under a deadline.

We all know that "testing is import". You may have been through a software training program where testing is tacked onto the end if mentioned at all. Or you might have taken the opportunity to review a small piece of the testing world that your company relies on to ship the product successfully. With the right testing strategy, you’re going to need to consider a lot of layers (and we’re not talking just about everyone’s favorite Testing Pyramid).

Let's connect and share this journey together: https://linktr.ee/jessicarosentech