Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Scout/Concepts/Test

< Scout‎ | Concepts
Revision as of 13:51, 14 January 2013 by Jeremie.bresson.unblu.com (Talk | contribs) (RT.Testing)

The Scout documentation has been moved to https://eclipsescout.github.io/.

This Page describes the architecture we want to obtain for the Scout Test Infrastructure (Testing support: how to test a scout application, but also unit test for Scout RT and SDK). See Scout Roadmap for more information.

Please do not change the title of the sections


Demo

BSI has a small Demo Application (Client-side only) that displays all the fields. For the moment this application is closed source.

This application is useful to display all possibilities offered by the fields (common configuration for each field). There is no need to have this in the eclipse repository (no need for IP-Clear). Therefor the idea is to refactor the application publish it on github.

Nice to have: For each demonstrated field, we want to have a link to the GitHub java source code page.

Branch organization on GitHub should be the same as in the Eclipse Repository.

TODO

  • Find a name for the project: com.github.widgets-demo or something like that.
  • Create the repository in GitHub
  • Create a POC
    • one page for one field
    • with link to the source code at Git-Hub
    • built with Maven Tycho
  • create the rest of the pages (for the other pages) == migration of the current test application to the new widgets-demo application.
  • mention the project in the scout book


RT

The RT Code contains some classes used before JUnit (ITest, AbstractClientTest, AbstractServerTest, ...). This approach should no longer be used.

TODO

  • bug 397085: Mark legacy testing support as deprecated


RT.Testing

Theses plugins contains classes for testing support: this is a collection of classes (JUnit test runner, Utility, Abstract Test classes…) that can be used to write JUnit tests for Scout Applications.

Naming convention: please do not name the classes with a Test suffix. Prefer TestingSupport or something like that.

List of plugins:

  • org.eclipse.scout.rt.testing.client
  • org.eclipse.scout.rt.testing.shared
  • org.eclipse.scout.rt.testing.server
  • org.eclipse.scout.rt.testing.ui.rap
  • org.eclipse.scout.rt.testing.swing
  • org.eclipse.scout.rt.testing.swt

This plugins are exposed in a testing feature.

This plugins are also used in the RT.Test fragments (Theses tests are also using JUnit to write tests).

TODO

  • bug 376459: Add a testing feature and publish it on the Scout update site

RT.Test

SDK.Test

SDK Test support

Back to the top