Hello #gnome people, are #gui tests still done through the #accessibility #api? I found discourse.gnome.org/t/how-do-y… but havent yet a chance to use #openQA or #dogtail. Im asking mostly because Im planning on making some small application, and I would like to add at the end of the CI pipeline some #end2end #test to make sure there are no regressions when attempting on some #datadriven #dynamic layout generation. Or in GNOME case e2e tests are generally not done for specific applications, and they are mostly for the shell, and applications are tested (mostly) by hand? (not trying to belittle #QA people, just I feel the common use cases should be automated to lessen the burden on them)
How do you test a GUI application?
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.GNOME Discourse
Emmanuele Bassi
in reply to jablkoziemne • • •GUI tests are kind of pointless: testing that the toolkit is doing the right thing should be part of the toolkit's test suite, not your application's. There's no point in simulating a user click on a menu, or a button, and seeing what happens.
My suggestion, like I said on that Discourse topic, is to split UI and business logic, and then create a "mock" UI for your tests that calls the business logic.