Why I Started This 30-Day Side Project

I've been working as an SDET for years, and over time I've built a solid foundation in software quality and testing.

Some of the skills I already use include:

• Test Automation
• API & UI Testing
• Regression & Release Testing
• Test Strategy & Planning
• Debugging & Log Analysis
• CI/CD and Git
• Basic SQL
• Python and other programming skills
• Test Framework maintenance
• Risk Analysis & Troubleshooting
• Cross-team collaboration

Testing is already the strongest part of my skill set.
But at some point, I started asking myself:What's next?

Why Expand Beyond Testing?

One practical reason is growth

Simply writing more automated tests doesn't necessarily create the next level of engineering capability.
I wanted to expand my skill set instead of only going deeper into what I already know.
but I realized that becoming a pure Software Engineer isn't exactly what I want.
I don't enjoy coding just for the sake of coding...

What I enjoy much more is finding problems, understanding why systems fail, challenging their limits, and figuring out how to make them more reliable.

That's what led me to Test Infrastructure

Why Test Infrastructure?

Modern testing is becoming increasingly connected with software, infrastructure, CI/CD, cloud environments, distributed systems, hardware platforms, observability, and AI.

Instead of only asking: Does this feature work?

I'm interested in questions like:

• Can we run hundreds of tests reliably?
• What happens when workers fail?
• Why did a test fail only in CI?
• Can failures be automatically classified?
• Can AI help engineers investigate failures faster?

Test Infrastructure sits right at the intersection of these problems.

And that's exactly fit a good side project that I want to explore and get to know more.