The axe element will be the same each time, but you can do that without any AI shenanigans - just run it in a normal Playwright test.

My question was really about the page interactions and the assertions being driven by AI: if they are going to be generating different code every time the test runs, how can you have any confidence in the test not having false positives and false negatives at least some of the time, unless you read the generated script each time?

That sounds like a lot more work than just writing the test once in the traditional way (codegen or manually) and tweaking it only when there's a breaking change to the page.

If people are genuinely using this approach then there must be something I'm missing.