I am not planning to update UI driven tests of non UI fubctionality as I
fundamentally disagree with that approach. I will probably replace these
tests with a non-UI driven version when I have integrated my scalability
test framework into the acceptance test harness which will enable the
writing of sensible tests and leave UI driven tests for what they are best
for... Ie testing the ui

On Saturday, 24 May 2014, Ullrich Hafner <ullrich.haf...@gmail.com> wrote:

> Are you planning to update the test?
>
> Am Freitag, 23. Mai 2014 schrieb Stephen Connolly :
>
>> Well if the tests are non UI tests driven through the UI then they can be
>> overly brittle.
>>
>> @Kohsuke this is a case in point
>>
>> On Thursday, 22 May 2014, Ulli Hafner <ullrich.haf...@gmail.com> wrote:
>>
>>> Seems that the new plugin breaks the acceptance tests for the LDAP
>>> plugin:
>>>
>>> https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/test/java/plugins/LdapPluginTest.java
>>>
>>> Am 22.05.2014 um 17:12 schrieb Stephen Connolly <
>>> stephen.alan.conno...@gmail.com>:
>>>
>>> OK, so there is now rumoured to be a faster and better way to look up
>>> the groups that a user belongs to in the LDAP 1.10 plugin.
>>>
>>> I say rumoured because due to the complexities of Active Directory
>>> server configurations, one can never be quite sure until one has had a fair
>>> amount of testing.
>>>
>>> To that end, please could you set up a simple test Jenkins instance and
>>> upgrade to ldap:1.10 and configure the `Parse user attribute for list of
>>> groups` group membership strategy (again rumour has it that on Active
>>> Directory the attribute `memberOf` is the magic attribute.
>>>
>>> See if that ends up giving you the same JENKINS_URL/whoAmI list of
>>> groups as when you have the `Search for groups containing user` set with
>>> the filter being `(member:1.2.840.113556.1.4.1941:={0})`... though the 
>>> `Parse
>>> user attribute for list of groups` should be very very fast for login while
>>> the `Search for groups containing user` could take *ages*.
>>>
>>> Respond back here with your findings so that I can remove the Red text
>>> on the version history about this being a rumour
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>
>>
>> --
>> Sent from my phone
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to 
> jenkinsci-users+unsubscr...@googlegroups.com<javascript:_e(%7B%7D,'cvml','jenkinsci-users%2bunsubscr...@googlegroups.com');>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Sent from my phone

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to