[News.eclipse.test-and-performance] Re: How about testing performance of

[Mike Norman <mgn@xxxxxxxxxxxxx>]

Chris

I know exactly what you mean. Hyades, for example, now provides some 
some tests defined in itself, but they don't have a clear relationship 
with the build process. This drifted in and out of scope of the 
discussions when we were building the project proposal. The feedback 
from the board in an early review cycle of the documents was that the 
includion of this in the project was not appropriate at  this time.

The broad issue of concern here is the definition of builds, and then 
the testing thereof, and then the testing and certification of plugins 
against those builds. There are separate vendor builds and 
certifications in place or being developed and I think resolution at 
this level will have to precede the creation of a project. This is 
particularly problematic with the non-core elements, such as Hyades 
which may be included in one vendor's build and not another, and is a 
nightmare for plug-in vendors wishing to install into a number of 
vendors builds.

Mike

Chris Laffra wrote:
> I think this top-level project would be a great host to a project focusing
> explicitly on testing and performance profiling of Eclipse itself. The
> core.tools tools should be moved into that project, in addition to the
> automated regression test tools currently managed by the Eclipse build
> team.
>
> I happen to have worked on Eclipse profiling tools that would be perfectly
> hosted under this "Eclipse Plugin Performance" sub-project.
>
> Chris Laffra