| <div id="midcolumn"> |
| <h1>RCP Testing Tool</h1> |
| <p >RCP Testing Tool is a project for GUI testing automation of Eclipse-based applications. RCPTT is fully aware about Eclipse Platform's internals, hiding this complexity from end users and allowing QA engineers to create highly reliable UI tests at great pace.</p> |
| |
| |
| <section class="highlight key-features background-grey" style="margin:30px 0"> |
| <div style="padding: 30px 0"> |
| <div> |
| |
| <div class="col-md-15 highlight-content"> |
| <h1>Key features</h1> |
| <ul style="font-size:11px"> |
| <li><strong>Test case creation productivity</strong> – ability to record user actions at the same level of efficiency as manual script creation, ability to capture initial/final application state into reusable models for further state restoring/verification.</li> |
| <li><strong>First class support of Eclipse technologies</strong> – testing tool should be aware about 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.</li> |
| <li><strong>Intelligent runtime</strong> – automatic wait of UI-triggered background asynchronous operations (including jobs, display async/timer execs, decorations, databindings, text reconcilers, text hovers, and so on)</li> |
| <li><strong>Reliable results</strong> – elemination of false negatives and false positives by isolation of test cases from each other, independence on screen size/operating system, etc.</li> |
| <li><strong>Maintainability</strong> – test case artifacts should be easily modifyable to reflect UI changes and be version control system friendly</li> |
| <li><strong>Extensibility</strong> – provide APIs for extending tool in order to support custom widgets, contexts, reports and async primitives.</li> |
| <li><strong>Continuous Integration</strong> – CI Test Runner runs tests locally and in integration with Jenkins, Hudson, or other CI tools.</li> |
| </ul> |
| |
| </div> |
| <div class="col-md-9 highlight-img hidden-xs hidden-sm" style="margin-top:50px"> <a href="/rcptt/download"> <img alt="Eclipse Working groups" class="img-responsive" src="/rcptt/img/badge-rcptt.png"> </a> </div> |
| </div> |
| </div> |
| </section> |
| |
| <h3>Configuration</h3> |
| <p>The minimal required configuration of applications under test is as simple as browsing for a folder for binary AUTs or choosing a PDE launch configuration for AUTs from sources.</p> |
| <h3>Workflow</h3> |
| <p> A typical workflow to create a test case which should work in most cases looks like this:</p> |
| <ul> |
| <li>Capture an application state</li> |
| <li>Record test actions</li> |
| <li>Add assertions</li> |
| </ul> |
| |
| <p>More complex activities including test parameterization, extracting common pieces of functionality into reusable actions, writing test cases manually before UI, and test case debugging are also available. Developers can extend the tool's functionality to add record/replay support of custom widgets and capture/apply support of custom aspects of an application state.</p> |
| <div style="clear:both"></div> |
| <h1 class="text-center"><a href="/rcptt/documentation/userguide/getstarted"/>Get started</a></h1> |
| </div> |
