Wt

Hi Mark,

by default they are disabled, so nobody will be bothered by them, unless they manually enable them.
This is new since 4.10.2 to support OSS Fuzz. Essentially these are tests. They provide a lot of randomized data to our parsers. Those parsers are probed for crashed, memory leaks, and such.

Nice, I need to bring that into my workflow eventually. Is that part of WTTEST? Is there any documentation on WtFuzz or WtTest?

No, this is completely separate of any of our own tests. It's facilitated by Google and runs on their infrastructure.
It's possible to run this locally as well. So it could be incorporated in a build pipeline without involving Google.

For now we added this, but are still evaluating how handy it is.

Thanks for that!

How about WtTest as a stand-alone? That's been around for a while, right? I've been thinking I need to implement some kind of unit-test as my app nears production (and complexity!)

The test library has been around since the beginning of Wt.

For anything production related I would advise to create unit tests, and if possible integration tests.

oh! ok, I found it. https://webtoolkit.eu/wt/doc/reference/html/classWt_1_1Test_1_1WTestEnvironment.html#details

I had been putting "test" in the search bubble in the documentation area, but it was only showing Wt::WFlags.