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

Remove spurious heading

Browse source
This commit is contained in:
Luca Beltrame 2016-11-27 10:05:56 +01:00
commit 5f825c49f6
Signed by: einar
GPG key ID: 40C8281493B01C16
1 changed files with 0 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -13,8 +13,6 @@ tags:
title: Testing the untestable title: Testing the untestable
--- ---
## Treading on thin ice
Admit it: how many times you have seen "software from this branch is completely untested, use it at your own risk" when you checked the latest code from any FOSS project? I bet you have, many times. For any reasonably modern project, this is not entirely true: Continuous Integration and automated testing are a huge help in ensuring that the code builds and at least does what it is supposed to do. KDE is no exception to this, thanks to [build.kde.org](https://build.kde.org) and a growing number of unit tests. Admit it: how many times you have seen "software from this branch is completely untested, use it at your own risk" when you checked the latest code from any FOSS project? I bet you have, many times. For any reasonably modern project, this is not entirely true: Continuous Integration and automated testing are a huge help in ensuring that the code builds and at least does what it is supposed to do. KDE is no exception to this, thanks to [build.kde.org](https://build.kde.org) and a growing number of unit tests.
## Is it enough? ## Is it enough?