I would also recommend Acceptance Test Harness. Another getting-started option would be to take a simple plugin without test suites and to try to introduce full cycle of tests there. Git plugins (proposed by Mark) are also an option, but probably their internals are too complex.
For example, https://github.com/jenkinsci/conditional-buildstep-plugin has a limited test coverage, which could be improved. понедельник, 14 сентября 2015 г., 14:17:01 UTC+3 пользователь Kanstantsin Shautsou написал: > > I'm trying design some "AIT (advanced integrations test)" :D for > docker-plugin/crowd2-plugins that has no tests at all and doesn't fit into > JenkinsRule/ATH, but it requires time and jenkins knowledge (plus > suggestions from experienced devs) > https://groups.google.com/forum/#!topic/jenkinsci-dev/R2_tHJDF0KI . > > On Monday, September 14, 2015 at 7:03:42 AM UTC+3, Romain SOMMERARD 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/6adca031-2573-4aa5-af36-686f830649d8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
