Playwright

Uh, we did a lot of test automation.

Uh, we had around a million line of Playwright, just to give you an idea, uh, Playwright and, and, and some Appium, um, uh, technology-based, uh, scripts, around a million lines, and, and still we had issues.

And, and the issues were a mix of, um, cost, meaning not that many regressions, but it slows your innovation or issues of the product works really well, but it's not the intended functionality because you start to have a gap between the business and the needs of the business and the teams building it and testing it.

And so w-when we got into selling, um, this business with Jihad, we really thought, "Okay, we built a successful business, but we didn't build Unicorn." What, what could have been different if we wanted to build something bigger? And we both agreed that quality assurance was, was the single item that slowed, slowed us the most, uh, and that made every innovation harder as you scaling.

Uh, we would need to spend more time defining a job description, but absolutely quality architect is a good, good title, I think.

What, what do you think will disappear? What will be like a thing of the past?

I think writing, uh, writing, um, uh, Selenium scripts and Playwright scripts and, and I think, I think everyone can picture that as that's something of the past, definitely.

Um, at least the way we do it today.