The following blog will show you we keep our customers and developers happy with our rigorous QA process, including our tools and testing methods. I j

Testing Materialize: Our QA Process

submited by

Style Pass

2024-05-15 16:30:06

The following blog will show you we keep our customers and developers happy with our rigorous QA process, including our tools and testing methods.

I joined Materialize’s Quality Assurance (QA) development team over a year ago. Since our team is small, we have to be conscious about focusing our time on the most impactful testing and test tooling.

Our goal is to find issues in Materialize as early and as efficiently as possible, ideally before a pull request even lands. Despite our small team, Materialize has a huge surface area:

We support many of Postgres’ features. Materialize also has a complex compute engine based on Timely/Differential Dataflow for incremental results. As with any software, the interplay of all these different components can create friction.

While the end result of Materialize is a simple user experience, all of these internals require stringent testing and other QA measures to avoid regressions. Above all else, we want to keep our customers and developers happy. The following blog will show you how we do this, with an overview of the QA process at Materialize.