What you seem to suggest is that a project higher up the stack test against the base. I think that by construct this is true bearing the change of version of the base. What I'm more concerned about is the running the tests of the lower level project in the presence in an install that contains the higher level ones. For example run the platform tests with egit and wtp installed.
From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Mickael Istria Sent: July-04-13 6:12 AM To: cross-project-issues-dev@eclipse.org Subject: Re: [cross-project-issues-dev] 6 month release cycle On 07/04/2013 11:52 AM, Alexey Panchenko wrote: Ideally, all the project tests should be executed - using dependencies from the simultaneous release repository. Projects are free to execute their tests on output of aggregated repo. The process is technically accessible to any plugin developer: * Take a target Eclipse (for example M7 with everything installed) * Install your tests in this target Eclipse * Use Eclipse test application to run automatically your tests on this platform (./eclipse -application org.eclipse.test.uitestapplication ....) IMO, it's the responsability of the project to run those tests, not another step for the aggregation process. This could be a new requirement to signoff before the simultaneous release (By M7 with current yearly approach): "Run project tests on a full execution environment". -- Mickael Istria Eclipse developer at JBoss, by Red Hat<http://www.jboss.org/tools> My blog<http://mickaelistria.wordpress.com> - My Tweets<http://twitter.com/mickaelistria>
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
