webtau VS jqwik

To run the test, we will use WebTau command line tool. One way to install it is to use brew. Other options available in documentation Installation section.

testing tool: https://github.com/testingisdocumenting/webtau

Just in case, here is the tool I developed, open sourced and use daily at work: https://github.com/testingisdocumenting/webtau

For scenarios like yours I also tend to do black box testing. I maintain testing framework called webtau (https://github.com/testingisdocumenting/webtau) and I use it to test a variety of apps. Webtau uses Java or Groovy language to write tests. I use it to test apps written in python/go/java/typescript/etc. The beauty of black box testing is you don't care what tech was used to write the software.

The right url for this open source tool is https://github.com/testingisdocumenting/webtau

webtau - web test automation. test across REST-API/Graph QL/Browser/Database/CLI - https://github.com/testingisdocumenting/webtau/

I often use REPL mode in webtau tool (web test automation: https://github.com/testingisdocumenting/webtau). With the REPL mode I don't have to restart test suite from scratch and can trigger one call or one test at a time preserving the context.

Have you seen webtau (https://github.com/testingisdocumenting/webtau)?

See https://jqwik.net

Once we knew which property to use it was very straightforward to add a property-based test for it. We used the jqwik library. We like it because it has very good documentation and it is integrated with Junit.

Jqwik - I love property based testing and the way it can make you think differently about some of your code.

Different to mutation testing, but on a semi-relatednpath, I've found property-based testing (e.g. https://jqwik.net/) to be valuable - thinking about the “shape“ of the expected output and getting a bunch of pseudorandom tests is pretty handy, especially for utility functions.