User Guide

Get started or use a menu on the right to jump to a relevant section.

Monday, Jan 1, 0001

Test Case Editor

Test case editor is the main editor for creating, running and executing test cases. Hover mouse cursor over the screenshot below to get context help. Test case name. This name is automatically synced with file system name. Symbols in name which are not allowed in file names are replaced with underscore character. Comma-separated list of arbitrary hierarchical tags, i.e. resourcePerspective, jira/PC-1352, windows-only Use this button to open tag selection dialog with list of tags from another test resources.

Monday, Jan 1, 0001

Test Runner

You can download it here. RCPTT Test Runner tests Eclipse-based applications by executing RCPTT tests unattended, on a regular basis. It provides a command line interface and a Maven plugin and establishes seamless integration of your GUI tests with your favourite toolchain. RCP Test Runner Arguments. RCPTT Maven Plugin. Runner is required to manage test bases greater than a dozen of tests for projects that care for development speed. Completely automated testing Command line interface Maven plugin Works with Jenkins, Hudson, Bamboo, etc.

Monday, Jan 1, 0001

Verifications

A good functional test can be represented like this: Therefore, a test case takes an system under test in some well-defined state, performs some actions, which transfer a system into another state, and then verifies that the final state is correct. Thus, in a test case we need to specify the following: Initial state Actions to perform Expected final state Since the very beginning RCPTT had support for declarative description of an initial application state via contexts, and imperative scripting language describing user actions, but there were no efficient way to verify a final state of an application - assertion statements in scipt look very bulky and not very readable, they cannot be reused and it might take way too long to add assertions for all aspects we want to check.