Thanks for clarifying. I agree. That is why WebTau examples by default are in Groovy (scripting language that runs in JVM). And WebTau has a simple way to define tests in files without need for IDE or setup.

Very impressive about your daughter writing test scripts!

The beauty of WebTau browser module is it provides very minimum wrapping on top of Selenium and you always have access to `driver` if you need it. The majority of wrapping is around stable elements exceptions and rich reporting.

However WebTau has other modules and it shines when you have a bit of cross layer interactions. My favorite is to use HTTP module to setup some data and then use browser module to simulate user actions. Or use `server` module to create proxy servers and fake servers to simulate hard scenarios in a multi server setups. There are other things as well.

Unfortunately I can't show you the best examples of run history as they are behind corporate wall. But WebTau build history itself is a good indicator. I use WebTau browser module to test WebTau generated web reports (which are single page apps with rich UI)