1
0
Fork 0
This commit is contained in:
Luca Beltrame 2016-11-27 10:27:18 +01:00
parent 043be07a9d
commit a7dd503e48
Signed by: einar
GPG key ID: 40C8281493B01C16

View file

@ -39,4 +39,4 @@ Is it enough to test the full experience of KDE software? No, but this is a good
Of course not. Automated testing only gets so much, so this is not an excuse for being lazy and [not filing those reports](https://bugs.kde.org). Also, since the tests run in a VM, they won't be able to catch some issues that only occur on real hardware (multiscreen, compositing). But is surely a good start to ensure that at least obvious regressions are found before the code is actually shipped to distributions and then to end users.
What needs to be done? MOre tests, of course. In particular, Plasma regression tests (handling applets, etc.) would be likely needed. But as they say, *every journey starts with the first step*.
What needs to be done? More tests, of course. In particular, Plasma regression tests (handling applets, etc.) would be likely needed. But as they say, *every journey starts with the first step*.