Need more UI/integration testing on simpler Eclipse baselines, to catch missing runtime dependencies causing disabled/broken functionality ------------------------------------------------------------------------------------------------------------------------------------------ Key: JBIDE-15167 URL: https://issues.jboss.org/browse/JBIDE-15167 Project: Tools (JBoss Tools) Issue Type: Bug Components: integration-platform, testing-tools Affects Versions: 4.1.0.CR1 Reporter: Nick Boldt Fix For: 4.2.x As exposed in JBIDE-15156, it's possible to successfully install parts of JBT into an Eclipse instance, but then have the JBT functionality missing due to missing undeclared runtime dependencies. Tycho will catch missing *build-time* dependencies, but doesn't know about *run-time* dependencies. Thus, to avoid JBIDE-15156 and similar (or undiscovered) problems in future, we ought to have Jenkins jobs that do this: a) for a given matrix of Eclipse platforms (platform runtime binary, Classic, Java, JavaEE), perform headless install (unpack) b) install a group of JBT features (eg., Server features, Forge features, GWT features, etc.), or install each update site category (core tools, web tools, mobile tools, cloud tools, general tools, reporting tools, etc.) c) run SWTBot JUnit tests in that Eclipse instance to verify that UI and functionality are present and working as expected.