On 07/04/2013 12:34 PM, Pascal Rapicault wrote:
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.
Not exactly, what I'm suggesting is that a project run test against *all
the content* of the release train installed. Some will be dependencies
and are anyway necessary for test to start, some other are independent,
and may interact with the project in an unexpected way.
Any project contributor takes an Eclipse, installs all Kepler bundles
(EGit, Subversive, WTP, m2eclipse, GMF, XText...) with the magic "Select
All" button of p2 installer, then it runs the tests against this huge
platform. That's how project can notice, additionally to their
acceptance tests validation product functionality, some "integration"
bugs such as conflicting jobs/builders and can guarantee that it works
together with the whole release train.
--
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
