Thank you all for your replies and insights! 

Ullrich, I totally agree with splitting tests but putting them into plugins 
would increase work for maintainers and contributors (as was mentioned by 
Mark). So in that case I wanted start with plugins which maintainer is 
aware of ATH and does not mind to do it. So your proposal is great, we can 
start with analysis plugins - choose the one plugin and see how it works if 
you agree. I will create jira for it. If it goes well, we can move tests 
into more plugins. 

Oliver, do you wish to move all tests of plugins from ATH or just those 
which are not very interesting from integration point of view (for example 
let there 1-3 tests for the most used scenarios of plugin which have a lot 
of installation)? I would let in ATH a few interested scenarios for most 
used plugins. On the other hand it is not such a problem to run the 
selenium tests for the most used plugins separately. What do you thing 
about it?

Martin, it sounds great. You can count with me anytime you need any help 
with it.

Regards,
Lucie


-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/c8f2b5aa-4259-4d75-91f9-d910ad5341b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to