The requirement for test cases going forward is good to see. Is there also an API versioning plan for future changes that may be backwards incompatible?
So far we had only talked about getting it to 1.0 to match Inkscape's release version. After that we'll start depricating older stuff depending on what we see in the wild. Since we've never done this kind of thing before, we don't know how the community of extension developers will respond.
Is this something that can be run in the gitlab CI and posted somewhere automatically? If not, how do I run the test suite, is it just done via the 'python3 setup.py check' in the extensions module, or is there another way to run it?
It's already running in the CI pipeline, it's failing. But it's running. So hopefully when all the specific issues with pytest and py2/3 are worked out (I noticed for instance that a failure happens in jessyink because Inkscape isn't available on the CI builder, but is on my machine, so doesn't fail for me)
The command is pytest, and you can specify some good options.
Best Regards, Martin Owens