Hi Romain, great to hear!
It's probably a good idea for you to look at the acceptance test harness[1] and improve its coverage of Jenkins features. There should be a lot of low hanging fruit in there, especially tests for plugins. Look to plugin popularity[2] if you don't know how else to prioritize. Daniel 1: https://github.com/jenkinsci/acceptance-test-harness 2: http://stats.jenkins-ci.org/jenkins-stats/svg/201507-top-plugins1000.svg On 14.09.2015, at 06:03, Romain SOMMERARD <[email protected]> wrote: > Hi guys, > > We are a team of 3 Master students who want to contribute to Jenkins test > case. > I come to you because I want to know if you have sections which have low test > case coverage or need improvement? > > Regards, > -- Romain > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/9ff27e72-2a2f-4203-9694-579ac05a2190%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8C5335B5-2F0F-415F-9225-876B14119207%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
