http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7593
--- Comment #48 from Jared Camins-Esakov <[email protected]> --- (In reply to comment #47) > I do not know how Jenkins is working. Does it precise which test is wrong? Jenkins just has all the sample data on a Debian Squeeze server and runs the entire build/test process every time there is a change to the source code. http://wiki.koha-community.org/wiki/Continuous_Integration If you look at http://jenkins.koha-community.org/job/Koha_master/lastCompletedBuild/testReport/ it gives you a summary, and you can get a bit more information in the log at http://jenkins.koha-community.org/job/Koha_master/lastCompletedBuild/console > The reason why I added unit test is that P. Poulain said me "new function, > new unit test" during Hackfest (the new function was on an other bug at that > time) ;-) > > So, you can suppress some of these tests if you think they are not > necessary... The test is definitely necessary, and looks good. I would not have pushed it without unit tests. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
