jablkoziemne<p>Hello <a href="https://101010.pl/tags/gnome" class="mention hashtag" rel="tag">#<span>gnome</span></a> people, are <a href="https://101010.pl/tags/gui" class="mention hashtag" rel="tag">#<span>gui</span></a> tests still done through the <a href="https://101010.pl/tags/accessibility" class="mention hashtag" rel="tag">#<span>accessibility</span></a> <a href="https://101010.pl/tags/api" class="mention hashtag" rel="tag">#<span>api</span></a>? I found <a href="https://discourse.gnome.org/t/how-do-you-test-a-gui-application/3010/3" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="ellipsis">discourse.gnome.org/t/how-do-y</span><span class="invisible">ou-test-a-gui-application/3010/3</span></a> but havent yet a chance to use <a href="https://101010.pl/tags/openQA" class="mention hashtag" rel="tag">#<span>openQA</span></a> or <a href="https://101010.pl/tags/dogtail" class="mention hashtag" rel="tag">#<span>dogtail</span></a>. 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 <a href="https://101010.pl/tags/end2end" class="mention hashtag" rel="tag">#<span>end2end</span></a> <a href="https://101010.pl/tags/test" class="mention hashtag" rel="tag">#<span>test</span></a> to make sure there are no regressions when attempting on some <a href="https://101010.pl/tags/datadriven" class="mention hashtag" rel="tag">#<span>datadriven</span></a> <a href="https://101010.pl/tags/dynamic" class="mention hashtag" rel="tag">#<span>dynamic</span></a> 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 <a href="https://101010.pl/tags/QA" class="mention hashtag" rel="tag">#<span>QA</span></a> people, just I feel the common use cases should be automated to lessen the burden on them)</p>