| [general] Plugin testing methology [message #148575] |
Sun, 14 March 2004 08:07 |
Eclipse User |
|
|
|
Hi there,
sure I know this is a general question but I am a bit puzzled about it.
Well I am used to test everything using unit tests. Those every class gets
its own TestCase and every public method at least one single test (method).
If the class is intended to be subclassed, every protected method gets also
its own test method and the class is mocked to ensure the contract
of the protected method (when its called etc.) is met.
But checking some test suites (exspecially the JUnit test suite) of Eclipse
I noticed quite a diffrent test behaviour. Its more like acceptance tests
in a more general way. Looks like it is setting up a scenario, let the
plugin does its work and check the results. There is no such fine-grain
testing going on.
Can anyone give me some informations about proper plugin testing
(when to write a test, what should be tested and what shouldn't etc.)
or point me to some resources I should read in order to understand it.
Thank you very much,
Martin (Kersten)
|
|
|
Powered by
FUDForum. Page generated in 0.07013 seconds
Home