Bug 553837

Summary:	[Tests] Restructure o.e.ui.tests
Product:	[Eclipse Project] Platform	Reporter:	Rolf Theunissen <rolf.theunissen>
Component:	UI	Assignee:	Platform-UI-Inbox <Platform-UI-Inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	Lars.Vogel
Version:	4.13
Target Milestone:	---
Hardware:	PC
OS:	Windows 10
Whiteboard:

Description Rolf Theunissen

2019-12-05 14:48:56 EST

I think that the current state of o.e.ui.tests is quite messy:
- The hierarchy of some TestSuites is different than the package hierarchy. That is, suites include tests from other packages.
- Manual, automated and session tests are mixed.
- Testcase classes and helper classes are mixed in packages.
- It is very hard to find relations between production code and test code. The test code hierarchy does not match the production code.

Because of this I think it is hard to get a clear view on what is tested and where it is tested. This makes it less then trivial to see which tests need to be extended when changing production code. This must especially be true for newcomers.
Also spotting that some tests are disabled is very hard. There are some test cases that have not been enabled for *17* years.

Do others agree? And if so, what should the structure of the tests be?

Comment 1 Lars Vogel

2019-12-05 15:23:17 EST

+1 for restructuring. As you have most likely the best insight due to your Junit 4 work, please do as you think is best.