| Summary: | Scout Client Testing Framework | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Adrian Moser <trekking09> |
| Component: | Scout | Assignee: | Project Inbox <scout.core-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | Andreas.Hoegger, jeremie.bresson |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 402308 | ||
| Bug Blocks: | |||
|
Description
Adrian Moser
Can we base this framework on JUnit @Rule instead of Abstract classes ? https://github.com/junit-team/junit/wiki/Rules http://www.alexecollins.com/?q=content/tutorial-junit-rule @Rule is usually used to create test context or inject context, so I do not currently see how it would help with providing an extendable default test itself. Or can you give some more hints? The GUI Tests should replace previous non-junit based client tests: see org.eclipse.scout.rt.client.services.common.test.AbstractClientTest. Please describe how they should be replaced and define a release when the deprecated tests should be removed. (see Bug 401179). Scout Project clean up. Bugs matching one of the following criteria will be removed: - SWT, Swing and HTML(RAP) bugs which are not mandatory for the next release. The future is the new HTML UI. - Bugs concerning a replaced technology. - old bugs which got obsolete. |