The SDET Notebook is a first-person testing blog about the parts of automation work that rarely fit neatly into tool documentation.

I write from the point of view of an SDET who spends a lot of time thinking about Selenium, Playwright, CI/CD pipelines, flaky tests, test data, selectors, reporting, and the newer wave of AI testing tools. The goal is not to hype every framework or pretend there is one correct stack. It is to document what actually helps when you are trying to keep a test suite useful after the first exciting demo.

You will find practical notes here: debugging patterns, tool comparisons, setup walkthroughs, review-style posts, and opinions formed from building and maintaining automated tests. Some articles are written for testers moving deeper into code. Others are for developers or engineering leads trying to understand why their end-to-end tests keep breaking on release day.

This site is intentionally personal. When I say a tool feels productive, brittle, confusing, or worth another look, that is based on hands-on use, reading the docs, building small examples, and comparing it against the problems SDETs commonly face.