[owickstrom]

Did you have a look at the intro in the manual? https://antithesishq.github.io/bombadil/1-introduction.html

If that's not clear, please let me know how we can improve it!

[sequoia]

"Bombadil is property-based testing for web UIs, autonomously exploring and validating correctness properties, finding harder bugs earlier."

I can't make heads or tails of this. What does it do? "Bombadil checks each property as it explores your system in its chaotic ways, reporting back any violations." what properties? checks how? does it read application state? "recording violations" what violations? "select an action and performs it" what actions?

This needs some code example, or a video, or something to explain what this tool is

The page "Language features > Properties" starts to explain what this is.

[darkvertex]

A hello-world example of what it looks like, and what running it would validate, would be nice.

It's all very abstractly described in the README and that intro page you linked.

[owickstrom]

Fair enough! I'm probably doing a demo video that'd help with this. Maybe can condense that in text form into the readme as well.

[maxwg]

> Bombadil itself decides what is an interesting event and when to capture state.

It would be very nice to have a little more details on how this works. Though I guess we can figure it out via code/trialing it out.

I'll give it a go later today!

[owickstrom]

Go for it! I've been meaning to do an "architecture of Bombadil" blog post that'd likely answer this question. It's not super advanced by any means, but it's a mindset shift to how you might think about browser testing coming from the mainstream frameworks like Playwright.