News for hackers. Stuff that matters.
Re:How the Claude Code team thinks about verification by simianwords on Tuesday November 17, 2026 @06:52AM (#50530219)
Its almost become a meme at this point: well actually you can achieve the same using X so why west tokens?!

The reason you should use Claude and not playwright always is because the the invariant you wanna capture is at the natural language level.

Like imagine I wanted to verify that Claude Code works and doesn't break. I can describe the invariant I want in natural language. Like: make sure that subagents don't block the original thread.

Doing this in playwright means that you have already bought into some previously existing architecture which means your tests are now correlated to your code. Having the invariants written in natural language allows you to decouple code vs the invariant.

I expect a lot of greybeard conservative programmers to keep opposing using AI here until eventually, not using AI will be seen as more risky.

Re:How the Claude Code team thinks about verification by LelouBil on Tuesday November 17, 2026 @07:02AM (#50530296)
[delayed]
Re:How the Claude Code team thinks about verification by fingerlocks on Tuesday November 17, 2026 @07:47AM (#50530684)
[delayed]
Re:How the Claude Code team thinks about verification by simianwords on Tuesday November 17, 2026 @12:05PM (#50534507)
If you re architecture threads to processes, you have to rewrite your tests.

That was kind of my point. Natural language almost always survives rearchitectures because your higher level interface to your end customer rarely has churn.

In a few years, agent driven testing will become normal and almost expected in some enterprise companies. Obviously we will still have people like you opposing it on grounds of “but just write tests in playwright”.

I also find the greybeard archetype fascinating. They’ve opposed almost everything new including Cloud, microservices, kubernetes. Now with AI. And here in this thread with AI driven tests. They seem to think programming should be done exactly how it was done when they were in the prime of their career. Anything before that is archaic and anything after is hype.

Re:How the Claude Code team thinks about verification by jimbokun on Tuesday November 17, 2026 @05:35PM (#50539248)
There were also a lot of massive cost overruns and technical debt accrued by people applying those things where they weren’t needed.
Re:How the Claude Code team thinks about verification by simianwords on Tuesday November 17, 2026 @06:06PM (#50539519)
Maybe. But these new concepts won and they weren’t just hype. They have their place. I’m obviously not saying AI testing has no wrong way of being used.

I’m saying that a default response to challenge AI testing by saying “just write normal tests” is the typical greybeard archetypical response. And they don’t really have a good track record considering they’d by default challenge cloud, kubernetes etc

Re:How the Claude Code team thinks about verification by jaapz on Tuesday November 17, 2026 @05:11PM (#50538971)
Don't know about you but my Claude uses playwright to verify everything works, playwright MCP is great!
Re:How the Claude Code team thinks about verification by simianwords on Wednesday November 18, 2026 @12:15AM (#50542143)
Does Claude create a new playwright each time? If not, how does it know when to change it when the underlying architecture changes?

If yes, that’s what I recommended.