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

Bug 364662

Summary:	Let client tests use real resources
Product:	[RT] RAP	Reporter:	Ralf Sternberg <rsternberg>
Component:	RWT	Assignee:	Project Inbox <rap-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	1.5
Target Milestone:	1.5 M4
Hardware:	PC
OS:	Linux
Whiteboard:
Bug Depends on:
Bug Blocks:	351769

Description Ralf Sternberg

2011-11-23 18:17:43 EST

The client tests currently use a servlet that delivers all resource files listed in the ClientResources class.
Since theming definitions are not included, those have to be copied manually after every theme change.

The test results would be more meaningful if they used the exact resources from a running RAP instance.
This would also allow us to run the tests in development and production mode. Theme changes would not break the tests anymore.
And, we could easily deploy our tests on the demo server (bug 351769).

Comment 1 Ralf Sternberg

2011-11-23 18:26:19 EST

The client tests now start a RAP application that provides the resources. A service handler returns the actual resource locations for the client library and the default theme.

Comment 2 Ralf Sternberg

2011-11-28 08:16:18 EST

It turned out that this change made test-driven development difficult, since the test server needs to be restarted after every change. Moreover, having separate JavaScipt files makes debugging easier on the client.

Therefore I re-installed the ClientResourcesAdapter and let the ClientResourcesServiceHandler deliver the resources. With this change, the theming resources are still loaded from a live RAP application, so the tests don't have to be adjusted after theming changes. It is still possible to deploy the js tests on a server.