My First Time Setting Up a Pipeline
Setting up my first CI/CD pipeline was a mix of excitement and confusion. I’d written automation tests locally, but getting them to run automatically on every commit felt like a huge leap.
Setting up my first CI/CD pipeline was a mix of excitement and confusion. I’d written automation tests locally, but getting them to run automatically on every commit felt like a huge leap.
Automated tests are great when they work — but I quickly learned they can be frustratingly unreliable if you’re not careful.
Automation once felt like an abstract concept to me — something you learn from tutorials and theory but don’t fully grasp until you actually build something real.
Automation testing is amazing. It speeds up feedback loops, reduces repetitive work, and helps catch regression bugs early. But despite my love for automation, I firmly believe manual testing still plays a critical role in quality assurance.
When I first dipped my toes into test automation, I was immediately faced with a huge range of tools to choose from. Selenium had been the industry standard for years, but newer frameworks like Cypress and Playwright were gaining traction fast. I wanted a tool that was modern, easy to work with, and powerful enough to handle all the testing challenges I’d encounter.