https://arran4.github.io/blog/tags/ai-agents/Recent content in ai-agents on Arrans Technical blogHugo -- gohugo.ioentechnicalblog123@arran4.com (Arran Ubels)technicalblog123@arran4.com (Arran Ubels)Arran Ubels. This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution-ShareAlike 4.0 International License</a>.Fri, 28 Aug 2026 11:24:25 +0000https://arran4.github.io/blog/post/2026/040-programmable-ui-verification-seams/Fri, 28 Aug 2026 11:24:25 +0000technicalblog123@arran4.com (Arran Ubels)https://arran4.github.io/blog/post/2026/040-programmable-ui-verification-seams/When testing server-rendered web applications, there is a common trap: relying on full end-to-end browser automation (like Selenium or Playwright) to verify simple presentation logic. If you want to know how a page renders when a user has no permissions, you often have to spin up a database, migrate it, insert seed data, authenticate a user, navigate to the page, and then assert against the DOM. This is slow, brittle, and introduces a massive amount of unrelated state (database connections, routing, session management) just to answer a simple question: Does this HTML template render correctly?