Community
Participate
Working Groups
Consider support for TestNG either as an optional test component or perhaps as the primary test harness. (TestNG is capable of executing JUnit and JUnit4 tests.) Justification: TestNG has real advantages both for test development and test execution. As one use case, we do a lot of testing of code generation and need the capability to load and execute test classes dynamically. TestNG's support for factories, DataProviders and parameterized tests along with a more sophisticated dependency model. On the harness side, TestNG's support for distributed and parallel testing could significantly improve overall unit testing performance on multi=processor system. I'm currently employing TestNG for internal application testing and am getting 8x (linear) speedup on my test suites on dual quad-core Mac Pro. :) With distributed testing, platform could see a major improvement in build cycles. (I can't imagine that this would make it into 3.5, so I'm going to mark it as 3.6 unless someone is really inspired.)
Miles, each Eclipse project takes care of its own release engineering and test infrastructure. This component is for the Eclipse top-level project release engineering (http://eclipse.org/eclipse/). Unless there is some demand for this from Eclipse project developers, or the platform release engineers think this will make their lives easier, this won't be addressed. For parallel testing, we are currently constrained by the number of available test machines rather than a lack of ability to run tests in parallel.
OK, thanks John sorry for OT then. I had thought that any Eclipse hosted project contributions would need to use standard build process, and therefore commit to JUnit only in order to use the Eclipse automated build for the 3.6 release train. I understand you to say that this is only for JDT, PDE, RCP, but not say Modeling or BIRT distro and/or update sites. I'll address all of this with project PMC / mentors. This is a really just a nice to have anyway -- a marker for anyone else interested. I'll put this in Dash as Kim Moir suggested on platform-releng-dev.
Assigning to CBI for consideration.
Cool, thanks Wayne!
Deferring this to CBI 2.0. We'll revisit once we have more core functionality complete.
Some of the mentioned features of TestNG are already (or will be) covered by JUnit4 or JUnit5 respectively. Since this is considered a "nice to have", I'm closing this issue. Please feel free to re-open if you want to pick this up.
