RCP Testing Tool

Key Features

• Test case creation productivity
  • ability to record user actions at the same level of efficiency as manual script creation, an ability to capture initial/final application state into reusable models for further state restoring/verification.
     
• First class support for Eclipse technologies
  • the testing tool should be aware of key concepts of Eclipse Platform, including but not limited to Workspace, Workbench, Preferences, Debug API, as well as understand the underlying UI structure, like parts of Eclipse Workbench (views, editors, toolbars) and structure of GEF/GMF/Graphiti diagrams.
     
• Intelligent runtime
  • an automatic wait of UI-triggered background asynchronous operations (including jobs, display async/timer execs, decorations, data bindings, text reconcilers, text hovers, and so on)
     
• Reliable results
  • elimination of false negatives and false positives by isolation of test cases from each other, independence on screen size/operating system, etc.
     
• Maintainability
  • test case artifacts should be easily modifiable to reflect UI changes and be version control system friendly
     
• Extensibility
  • provide APIs for extending tool in order to support custom widgets, contexts, reports, and async primitives.
     
• Continuous Integration 
  • CI Test Runner runs tests locally and in integration with Jenkins, Hudson, or other CI tools.