websites/dennogumi.org-archive
Archived
1
0
Fork 0
Code Releases Activity

Fix typo

Browse source
This commit is contained in:
Luca Beltrame 2016-11-27 10:26:46 +01:00
parent 9a96f57620
commit 043be07a9d
Signed by: einar
GPG key ID: 40C8281493B01C16
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
_posts/2016-11-27-testing-the-untestable.markdown
View file

@ -37,6 +37,6 @@ Is it enough to test the full experience of KDE software? No, but this is a good
## Is this enough for everything?
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.
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*.