There is a great thread earlier in the list which offers insights into the different facilities available to test a plugin, the concepts involved, and the related compromises.
Refer to https://groups.google.com/d/msg/jenkinsci-dev/R8w7uhh-xbg/Z3O5ew1NBwAJ Mark Waite On Tue, Oct 24, 2017 at 7:00 AM Valerie Fernandes <[email protected]> wrote: > Hi Guys, > > I need your advise to understand what is the best means to test Jenkins > plugins. > We have some plugins that were developed in house. To test the > functionality we have selenium tests per plugin. > Problem is that, these tests are time consuming, and often fail due to > timeout issues or element not found and could succeed on a rerun. > Additionally, changes in UI(could be due to Jenkins upgrade 1.x --> 2.x) > means we need to make changes in the tests as well. :( > > I see most Jenkins plugins have JUnit's. Can you suggest? > > -- > 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/c9c9e540-27c2-451d-9fc9-2c0562bef9db%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/c9c9e540-27c2-451d-9fc9-2c0562bef9db%40googlegroups.com?utm_medium=email&utm_source=footer> > . > 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/CAO49JtH9Pp1FLc0c9Grp1oeXrZWb17jDiffVDmVTepUX21v-5g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
