Thread: [Shinken-devel] Jenkins Shinken Tests
Status: Beta
Brought to you by:
naparuba
From: Sébastien C. <s.c...@fr...> - 2013-07-05 19:37:35
|
Hi everyone! Whereas some of you are working on 2.0 super features, I try to fix some small core bugs and work on tests. As Shinken is part of my job, I have some tools to ensure proper dev and test phases. I know that testing is always a long thing to do, and particularly with a crappy computer ;). As a result, I have set public the Jenkins builds of Shinken (which is pulled from nap git) so that everyone can see it! I created 2 builds : https://test.savoirfairelinux.com/job/Shinken-Upstream-Commit-Short-Tests/: This one launch the shorttests.txt tests at every commit on master. It is used to check if a commit is not breaking a big "thing" in Shinken https://test.savoirfairelinux.com/job/Shinken-Upstream-Daily-Full-Tests/ : This one lauches the all_tests.txt every 6 hours. This is the full test build for Shinken. I still have trouble to make the last one work. Actually, the test_livestatus_cache is failing which make the whole thing fail. I spent some time trying to fix it but without success. If one of you can help me to make it work i could be great. This test is broken since a long time, I dont even know if it worked a day. Maybe the test is just bad so that we have to rewrite it :) For the short test set, I'll need your opinion too. I took the file done by Gerhard, maybe we can add/remove important/useless tests. Some tests are critical for Shinken, we have to choose wisely ;) The Jenkins builds are read-only and unfortunately there is no way to add "guest" access (I asked, and Jenkins is not very compliant with multi-source authentication). If we manage to make the all_tests work, we will get some nice report about the code coverage. Every file use by Jenkins during tests is tracked so that we can have a cover percent per file. Of course the best is 100% :). Those report will help A LOT to find where tests are missing and so make Shinken more reliable! Code metrics are always great to see a project heath :). Best Regards, Sébastien COAVOUX, Computer Science Engineer (Network && Systems) Shinken Development Team Member GitHub <https://github.com/Seb-Solon> - Twitter<https://twitter.com/Seb_Cvx> - Linkedin <http://www.linkedin.com/profile/view?id=86578210> |
From: nap <nap...@gm...> - 2013-07-15 08:41:16
|
On Fri, Jul 5, 2013 at 9:37 PM, Sébastien Coavoux <s.c...@fr...> wrote: > Hi everyone! > > Whereas some of you are working on 2.0 super features, I try to fix some > small core bugs and work on tests. > As Shinken is part of my job, I have some tools to ensure proper dev and > test phases. I know that testing is always a long thing to do, and > particularly with a crappy computer ;). As a result, I have set public the > Jenkins builds of Shinken (which is pulled from nap git) so that everyone > can see it! > > I created 2 builds : > > https://test.savoirfairelinux.com/job/Shinken-Upstream-Commit-Short-Tests/: This one launch the shorttests.txt tests at every commit on master. It is > used to check if a commit is not breaking a big "thing" in Shinken > > https://test.savoirfairelinux.com/job/Shinken-Upstream-Daily-Full-Tests/: This one lauches the all_tests.txt every 6 hours. This is the full test > build for Shinken. > > I still have trouble to make the last one work. Actually, the > test_livestatus_cache is failing which make the whole thing fail. I spent > some time trying to fix it but without success. If one of you can help me > to make it work i could be great. This test is broken since a long time, I > dont even know if it worked a day. Maybe the test is just bad so that we > have to rewrite it :) > > For the short test set, I'll need your opinion too. I took the file done > by Gerhard, maybe we can add/remove important/useless tests. Some tests are > critical for Shinken, we have to choose wisely ;) > > The Jenkins builds are read-only and unfortunately there is no way to add > "guest" access (I asked, and Jenkins is not very compliant with > multi-source authentication). > > If we manage to make the all_tests work, we will get some nice report > about the code coverage. Every file use by Jenkins during tests is tracked > so that we can have a cover percent per file. Of course the best is 100% > :). Those report will help A LOT to find where tests are missing and so > make Shinken more reliable! Code metrics are always great to see a project > heath :). > > Best Regards, > > > Sébastien COAVOUX, > > Computer Science Engineer (Network && Systems) > Shinken Development Team Member > > GitHub <https://github.com/Seb-Solon> - Twitter<https://twitter.com/Seb_Cvx> > - Linkedin <http://www.linkedin.com/profile/view?id=86578210> > > Thanks a lot for all this work. Coverage will help us to find which part of the core is still without test. 100% will be impossible I think, but if we can get close, it can be a great step for the project! :D Jean |