Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 306339

Summary: [design] refactor unit tests for theming
Product: [RT] RAP Reporter: Holger Staudacher <holger.staudacher>
Component: RWTAssignee: Project Inbox <rap-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3    
Version: 1.3   
Target Milestone: 1.3 M7   
Hardware: All   
OS: All   
Whiteboard:

Description Holger Staudacher CLA 2010-03-18 06:00:59 EDT 
With the fix for bug 296227 we got unit tests for the design themes. Currently every property from all widgets is  tested in a separate test method. I would make sense to provide a framework which reads the expected property values and makes a comparison against the registered css.
Comment 1 Ralf Sternberg CLA 2010-03-18 06:40:19 EDT 
Instead of coding the expected property values for each element, style, state, etc. in Java code, we can create those "test plans" in CSS files. This reduces the amount of test code to write to one simple test case per theme.
Introduced a class ThemeTestCase that provides means to execute those CSS tests.
Comment 2 Holger Staudacher CLA 2010-03-23 05:53:43 EDT 
Fixed. Thanks to Ralf. Changes are in CVS HEAD now.