What is the testing story for pygobject vs what it could be ?
Writing pygobject based code, I find implementing a lot more tricky than what I do in my day job writing Django Apps.
Under django I have things like the test client, that I can fake up requests and trigger all the code in my views without needing a browser.
In my pygobject code, I can't work out how to test code paths without putting a GUI on the screen (and even then I would (probably?) have to write some bespoke code).
I can probably test things headlessly, with XVFB, though I don't know if that will continue to work.
There are a couple of parts to this -
I'd like to get some feedback if the above is true + what currently exists in pygobject (IE, there are probably a bunch of things that test pygobject itself that could be useful for users to track their code).
The other part - it would be good to collect a list of things that we can ask for from the people working on Gtk4, that would improve the test situation.
The main thing I feel is missing, is some sort of test client version of Gtk, that allows all theordinary calls without showing a window.