Hi, I’m Yoshi โ the author behind QA Auto Lab. I’m a QA engineer and test automation engineer with 15+ years of hands-on experience, specializing in test automation and CI/CD integration using Python, Playwright, Selenium, and pytest.
Over the course of my career, I’ve worked on multiple development projects โ web services, enterprise systems, and e-commerce platforms โ taking ownership of quality assurance and test automation from design through to operations. My experience spans E2E test infrastructure with Playwright and Selenium, API test automation, and CI/CD pipeline design.
On this blog, I write about test automation design, implementation, and CI/CD integration โ centered on Python, Playwright, and pytest. Everything is grounded in real-world practice, and I aim to share it in a way that anyone can reproduce from scratch.
The reason I started this blog: working as a QA engineer, I noticed a lack of practical, hands-on test automation resources in English that connected directly to real workflows. I’m particularly passionate about continuous quality improvement through Playwright, pytest, and CI/CD โ and I practice what I publish every day.
๐ค Profile
๐ก “Not unbreakable code โ but a system that notices when it breaks.”
15+ years of writing code as a developer, then breaking it as a QA engineer.
I believe test automation is a weapon for protecting quality.
| Name | Yoshi |
| Role | QA Engineer / Test Automation Engineer |
| Experience | 15+ years (QA, test automation, software development) |
| Tech Stack | Python / Playwright / Selenium / pytest / GitHub Actions |
| GitHub | https://github.com/YOSHITSUGU728 |
| https://www.linkedin.com/in/yoshi-baba-68b8a0375/ | |
| Published Languages | Japanese ๐ฏ๐ตใEnglish ๐บ๐ธใKorean ๐ฐ๐ท |
๐ Career Highlights
- 15+ years in quality assurance and test automation across web services, enterprise systems, and e-commerce platforms
- Background in web application development โ able to approach quality from both a developer and QA perspective
- Designed and built E2E test infrastructure using Playwright, Selenium, Python, and pytest
- Implemented and maintained REST API test automation (pytest ร requests / Playwright APIRequestContext)
- Integrated test automation into CI/CD pipelines with GitHub Actions, including automated Allure reporting
- Published working code on GitHub (automated-testing-portfolio) for reproducible, verifiable examples
- Publishing test automation articles in Japanese, English, and Korean on QA Auto Lab
๐ง What I Do
I cover the full spectrum โ from test automation design and implementation to CI/CD integration.
| Area | Details |
|---|---|
| E2E Test Automation | Browser automation and test script implementation with Playwright and Selenium |
| API Test Automation | REST API testing with pytest ร requests and Playwright APIRequestContext |
| Test Design | Page Object Model, fixture design, mark strategies, test pyramid architecture |
| CI/CD Integration | Automated test execution and Allure report generation with GitHub Actions |
| Reporting | Test result visualization and sharing with Allure Report and pytest-html |
๐ About This Blog
QA Auto Lab is a blog for engineers learning test automation โ delivering working code and practical knowledge from real-world experience.
๐ Topics I cover
- E2E test implementation with Playwright and Selenium
- pytest: fixtures, parametrize, and conftest.py in practice
- Test design patterns like Page Object Model
- CI/CD integration with GitHub Actions
- Setting up and using Allure Report
- QA career advice, test automation ROI, and real-world know-how
All code samples on this blog are verified in a real test environment before publishing. The code is also available on GitHub โ feel free to clone and run it yourself.
๐ก What This Blog Is Here to Do
- Make test automation more approachable for everyone
- Provide practical, reproducible code that beginners can actually run
- Share quality assurance knowledge in three languages to reach engineers worldwide
๐ Published Languages
Articles on this blog are published in Japanese, English, and Korean. The goal is to reach QA engineers and test automation learners not just in Japan, but around the world.
| Language | Category |
|---|---|
| ๐ฏ๐ต Japanese | ใในใ่ชๅๅ |
| ๐บ๐ธ English | test-automation |
| ๐ฐ๐ท Korean | ํ ์คํธ ์๋ํ |
๐ฉ Get in Touch
Questions about the blog, feedback, or technical questions about test automation are all welcome. Feel free to reach out.
๐ฉ Types of inquiries welcome
- Questions or feedback about articles
- Technical questions about Playwright, Selenium, or pytest
- Consultations on test automation design or adoption
- Writing or technical review requests
๐ Contact form
๐ฏ Areas of Expertise
| Test Automation | QA Engineering | Playwright | Selenium |
| pytest | Python Testing | API Testing | CI/CD |
* All code samples published on this blog are verified in a test environment before being shared.
๐ New here? Start with these
Test automation isn’t as hard as it looks. With the right approach, anyone can make it part of their workflow. I hope QA Auto Lab helps you take your first step โ or your next one. Let’s learn together. ๐