AI Testing 12 min
Claude Code Has 2 Primitives, Not 3 — Use Skills First
Most engineers think Claude Code has three primitives. It actually has two — skills and subagents. Here's when to use which, with token-cost benchmarks.
Read the story Currently writing · open to consulting
Test automation that survives production.
I'm Halmurat T. — senior SDET writing about test automation at enterprise scale. Fifteen years debugging production systems at Fortune 500 telecom, insurance, retail, and financial services. The kind of scars you can't read about in documentation.
This blog is opinionated by design. Playwright vs Selenium isn't a tie. Page Object Model is overengineered. Your flaky test isn't flaky — it's broken. If that sounds useful, stick around.
ship/ StepScout — IntelliJ plugin for Cucumber step navigation →
Don't miss a thing
Subscribe to get updates straight to your inbox.
No spam · Unsubscribe anytime
§02 Status board
§01 Recent writing
View all →
24 min
Stop Sharing Test Environments — Build One You Control
Shared staging environments are the #1 source of flaky UI tests in enterprise teams. Here's the 5-pillar blueprint for building a controlled test environment.
11 min
We Cut 150 Min of Test Setup with 3 Java Classes
How we built a Playwright API test data layer in Java — replacing UI setup that burned 150 minutes per run with 3 classes and a legacy API wrapping pattern.
13 min
Contract Testing vs API Testing — What's the Difference?
Contract testing and API testing look similar but they catch very different bugs. Here's where contract testing fits next to unit, API, and E2E tests.
13 min
Parallel Execution Without the Refactor Tax
Thread-level parallelism demands ThreadLocal and full framework rewrites. Process-level parallelism doesn't. Here's the difference and when to use each.
9 min
Stop Using locator() for Everything in Playwright
Most Playwright teams still use CSS selectors via locator() out of habit. getByRole and getByText find elements the way users do — and survive redesigns.