1
0
Fork 0

Fix links

This commit is contained in:
Luca Beltrame 2016-11-27 18:56:59 +01:00
parent a7dd503e48
commit 8404be5cbf
Signed by: einar
GPG key ID: 40C8281493B01C16

View file

@ -31,7 +31,7 @@ Those who use openSUSE Tumbleweed know that even if it is technically a "rolling
Indeed, this is not news. But the big news is that, thanks mainly to the efforts of Fabian Vogt and Oliver Kurz, now *openQA is testing also KDE software from git*! This works by feeding the Argon (Leap based) and Krypton (Tumbleweed based) live media, which are roughly built daily, to openQA, and running a series of specific tests. Indeed, this is not news. But the big news is that, thanks mainly to the efforts of Fabian Vogt and Oliver Kurz, now *openQA is testing also KDE software from git*! This works by feeding the Argon (Leap based) and Krypton (Tumbleweed based) live media, which are roughly built daily, to openQA, and running a series of specific tests.
You can see here [an example for Argon](https://openqa.opensuse.org/tests/309076) and [an example for Krypton]https://openqa.opensuse.org/tests/latest?test=krypton-live&arch=x86_64&flavor=Krypton-Live) (note: some links may become dead as tests are cleaned up, and will be adjusted accordingly). openQA tests both the distro-level stuff (the `console` test) and KDE specific operations (the `X11` test). In the latter case, it tests the ability to launch a terminal, running a number of programs (Kate, Kontact, and a few others) and does some very basic tests with Plasma as well. You can see here [an example for Argon](https://openqa.opensuse.org/tests/latest?test=krypton-live&arch=x86_64&flavor=Argon-Live) and [an example for Krypton](https://openqa.opensuse.org/tests/latest?test=krypton-live&arch=x86_64&flavor=Krypton-Live) (note: some links may become dead as tests are cleaned up, and will be adjusted accordingly). openQA tests both the distro-level stuff (the `console` test) and KDE specific operations (the `X11` test). In the latter case, it tests the ability to launch a terminal, running a number of programs (Kate, Kontact, and a few others) and does some very basic tests with Plasma as well.
Is it enough to test the full experience of KDE software? No, but this is a good solid foundation for more automated testing to spot functional regressions: during the openSUSE Leap 42.2 development cycle, openQA found several upstream issues in Plasma which were then communicated to the developers and promptly fixed. Is it enough to test the full experience of KDE software? No, but this is a good solid foundation for more automated testing to spot functional regressions: during the openSUSE Leap 42.2 development cycle, openQA found several upstream issues in Plasma which were then communicated to the developers and promptly fixed.