A new article is out on building a scalable test framework

I’ve just published a new post: “How we created a new test framework to scale it for the future”. In it, I explain why our previous test framework stopped scaling cleanly as more backend services, helpers, wrappers, and integration points were added over time.

Here’s what’s inside:

• 🧩 Why blurred layer boundaries and local workarounds gradually made the old framework harder to extend
• 🏗️ How we redesigned the architecture around explicit layers: facade, endpoints, models, domain helpers, and platform components
• 🔌 Why the new structure makes SDK integration, OpenTelemetry, and other cross-cutting tooling much easier to introduce
• 🤖 How clearer contracts and documentation improve the quality of AI-assisted code generation and code changes
• 🔄 Why we chose incremental migration into a new repository instead of freezing development for a risky in-place rewrite

If you work on API test automation, Python frameworks, or large backend systems, this article may be useful if you’re thinking not just about test coverage, but about how your framework will keep evolving as the team and tooling grow.

📄 You can read the article on Medium, Habr (EN), or Habr (RU)

🔙 Earlier article for context: “How we made Python/pytest suites 8.5× faster” on Habr