From 5f825c49f641618df5b0265609a1214c4bd933ed Mon Sep 17 00:00:00 2001 From: Luca Beltrame Date: Sun, 27 Nov 2016 10:05:56 +0100 Subject: [PATCH] Remove spurious heading --- _posts/2016-11-27-testing-the-untestable.markdown | 2 -- 1 file changed, 2 deletions(-) diff --git a/_posts/2016-11-27-testing-the-untestable.markdown b/_posts/2016-11-27-testing-the-untestable.markdown index f653c5d..549b797 100644 --- a/_posts/2016-11-27-testing-the-untestable.markdown +++ b/_posts/2016-11-27-testing-the-untestable.markdown @@ -13,8 +13,6 @@ tags: 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. ## Is it enough?