Re: [platform-core-dev] Testability experiment

["John Arthorne" <John_Arthorne@xxxxxxxxxx>]

I guess it depends on what you mean by a unit.  We certainly test units of API functionality... For almost every API interface there is a corresponding test class that has the same name as the API interface with the suffix "Test".  For example IFileTest is a unit test for IFile, IResourceTest for IResource, etc.  We then have non-API tests for significant sub-systems of the resource model, such as builder, the property store, data tree, etc.  These tests don't operate on individual classes, but groups of related classes.  I think to assume that the unit of testability always maps to an individual class is an unneccesary and unrealistic assumption.  Just my two cents...





Hi John,

Thanks for your response. It seems to me you are suggesting that no
unit testing is done for Eclipse, am I correct? Perhaps I should have mentioned
that the focus of my research is on unit testing, I apologize for the omission.

The selection of classes I made is somewhat arbitrarily based on the calculation
of a number of source-based metrics. I am now aware that a number of these classes
are a bit extreme in the sense that they do not have a well-defined functionality on
their own. Thank you for pointing that out to me.

Yours,
Magiel Bruntink