On Wed, Sep 16, 2015 at 2:49 AM Oleg Nenashev <[email protected]> wrote:
> 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. > > I think the git client plugin and the git plugin are great places to start because you could pick a bug report, create a test which shows that the bug is present, and submit a pull request to include that evidence of a bug. In the process, you will have learned about automated testing, command line git, JGit, the git plugin, Jenkins, and more. However, I'm biased... Mark Waite -- 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/CAO49JtHzs7OxMgZ_BAkiAB_Z1T0x77%2BhLPBrqDy%2BrtXqrwM9ow%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
