Porting tests to plone.app.testing and removal of legacy packages

Dear all

I made a little step forward in porting all tests of Plone core packages 
to plone.app.testing. In the past it was difficult to merge some of the 
PR because of inter-dependencies between the single packages.
I now created a separate branch of the coredev buildout [1] which uses 
all the plone.app.testing branches which are not merged to master yet.

If it is all green we can merge all packages together to the master / 
5.0 branch of coredev.

@tisto Can we have a jenkins job for this?

With the removal of PloneTestCase the following dependencies can be 
removed from Plone 5 too (and are already gone in my branch):

Products.CMFActionIcons
Products.CMFCalendar
Products.CMFTopic
Products.PloneTestCase
Products.CMFTestCase

One package I treated special: Products.ResourceRegistries. According to 
my information this will be removed from Plone 5. Am I correct here? I 
removed all the tests depending on PTC in a separate branch [2] to 
continue with the PTC removal. If this package should stay in Plone 5 we 
have to restore and port the tests to p.a.testing too.


Cheers
Tom


[1] https://github.com/plone/buildout.coredev/tree/tomgross-noptc2
[2] 
https://github.com/plone/Products.ResourceRegistries/tree/tomgross-notests


------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk