QA Engineer | Cloud & CI/CD Enthusiast | 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 things 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 + automated UI and 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
Testing
- Playwright (Chromium, Firefox, WebKit)
- Manual QA, exploratory testing
- API testing (Postman)
- Test case design & defect reporting
CI / Dev
- GitHub Actions (CI = Continuous Integration, originated in Agile/XP practices)
- Git, GitHub
- Node.js, TypeScript
Cloud
- AWS (EC2, IAM, Lightsail)
- Azure (App Services)
- GCP (IAM, projects, service accounts)
-
🧪 testsplaywright
Playwright CI UI testing with HTML reports, traces, screenshots, and videos
👉 https://github.com/vivaciousdove/testsplaywright -
📊 learning-tracker
Evidence-based learning tracker across QA, Cloud, Education, and Wireless RF
👉 https://github.com/vivaciousdove/learning-tracker -
☁️ cloud-resume-challenge
Cloud-hosted resume with infrastructure and automation
👉 https://github.com/vivaciousdove/cloud-resume-challenge
- Evidence > opinions
- Failures should be debuggable, not silent
- Tests are documentation
- CI is a gate, not a checkbox
Before software QA, I held technical and leadership RF Engineering roles, all responsible for network performance, optimization, and resolving customer-impacting issues.
That mindset still drives how I test:
- 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