QA Engineer | Cloud & CI/CD Enthusiast | Former RF Engineer
I’m a quality-driven technologist with a background in wireless/RF engineering and a current focus on software QA, cloud platforms, and CI/CD pipelines.
I build systems end-to-end, test them like a skeptic, and document them like a professional.
Think season-long stat sheet, not highlight reel.
- 🧪 Design and execute manual and automated UI + API tests
- ⚙️ Build Playwright test suites with evidence-first reporting
- 🔁 Implement CI (Continuous Integration) pipelines using GitHub Actions
- ☁️ Work across AWS, Azure, and GCP
- 🧠 Translate complex systems into clear, testable requirements
- Playwright (Chromium, Firefox, WebKit)
- Manual QA & exploratory testing
- API testing (Postman)
- Test case design & defect reporting
- GitHub Actions
(CI = Continuous Integration, originating from Agile / XP practices) - Git, GitHub
- Node.js, TypeScript
- AWS: EC2, IAM, Lightsail
- Azure: App Services
- GCP: IAM, projects, service accounts
End-to-end UI + API automation with Playwright, FastAPI, MySQL, and Allure reporting
👉 https://github.com/vivaciousdove/provisioning-workflow
UI automation and observability using Playwright with evidence-driven validation
👉 https://github.com/vivaciousdove/playwright-cloud-status-dashboard
These projects serve as technical proof points for the QA/SDET capabilities described on my resume.
Click to view 👉 https://vivaciousdove.github.io/myresume/
- Evidence > opinions
- Failures should be debuggable, not silent
- Tests are living documentation
- CI is a quality gate, not a checkbox
Before software QA, I held technical and leadership roles in RF engineering, responsible for network performance, optimization, and resolving customer-impacting issues.
That mindset still drives how I test software:
- Root cause over symptoms
- Reproducibility matters
- Customers feel bugs before dashboards do
- GitHub: https://github.com/vivaciousdove
- Medium: https://medium.com/@tconnercloudandqa
- LinkedIn: https://www.linkedin.com/in/todd-conner