You've described the strategy that I prefer.

Mark Waite

On Wed, Oct 25, 2017 at 3:04 AM Valerie Fernandes <[email protected]>
wrote:

> Thanks Mark,
>
> So what I understand is,
>
>    - Primarily use JUnits based on JTH in order to run most of the tests
>    for functionality.
>    - Use ATH minimally for testing the integration of plugins with each
>    other
>
> Please correct me if I have understood incorrectly.
>
> On Tuesday, 24 October 2017 18:44:00 UTC+5:30, Mark Waite wrote:
>
>> 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/421affea-5557-43a1-8da0-41d6cfdb2c81%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/421affea-5557-43a1-8da0-41d6cfdb2c81%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/CAO49JtFqC61vAifk4zxBb0ChjaqFY7-oBLPaZbtQ8ju572NTKA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to