Hi, I was doing some work to improve the CI system for our Erlang bindings and wondered what the best practice might be regarding the use of the bindingtester.py code in an automated CI run. I see that there’s a deterministic scripted test that’s the default, and other tests like api that pick a random api_version and seed on startup. I also seemed to find that the scripted test only supports the latest API version (at least, it still seemed to be testing newer functionality regardless of the value of --api-version that I passed to the script).
Are there any pointers to how the in-tree bindings go about their testing that might be useful to replicate?