testing UIs and improving a11y all at once!
Harald Sitter
sitter at kde.org
Tue Aug 16 13:45:07 BST 2022
On Tue, Aug 16, 2022 at 12:30 PM Arjen Hiemstra <ahiemstra at heimr.nl> wrote:
> Have you thought about how to integrate this into our projects? Ideally I
> suppose we would have the tests as part of each project's repo, but that might
> not work for things like Plasma, where running things depend on a lot of other
> dependencies. On the other hand having some sort of "plasma-tests" repo is
> much more likely to lead to unmaintained tests. But maybe we can tie things
> together with Gitlab pipeline triggers?
Good question. I suppose it depends a bit on the test, but, yeah, I'd
stay away from a standalone repo we can ignore. We'll have to see how
complex testing plasma really is. In theory we only need to
startplasma in xephyr or something, all the relevant bits and bobs are
kind of already part of the CI dependencies anyway. In particular kwin
and kded come to mind. All that being said, tests that only test a
single applet probably can just run plasmawindowed and call it a day.
HS
More information about the Plasma-devel
mailing list