Workbench Contexts

Workbench contexts are used to control perspective, views and open editors of application under test

Context 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

All you need to know about adding tags

Make a snapshot of all current AUT perspective, opened views and editors and copy them into this context.

Opens given perspective, views and editors. If Reset perspective option is on, resets perspective to its default.

All you need to know about Description

Click this button to erase current description contents

A perspective which should be open in AUT

Shows a perspective selection dialog populated with list of perspectives available in AUT

Whether to reset perspective to its defaults after opening

Close all modal dialogs if any

Clear clipboard contents

List of views which should be open. Also workbench context processor clears selection in views listed here.

Opens a view selection dialog populated with list of views from AUT (so there's no chance to enter an invalid view id)

List of editors to be open in AUT

Allows to select a file from current RCPTT Project's workspace contexts to be open in an editor

Introduction

The Capture button in the upper-right corner lets you automatically capture the current workbench state of your AUT. However, you can customize your workbench context using the settings listed below:

• Perspective id - the perspective to be open in AUT before running the test. Use the Browse button to view the user-friendly list of all perspectives available in AUT
• Reset perspective - when this option is checked, the AUT perspective will be reset to its own defaults
• Close all modal dialogs - when this option is checked, the workbench context will close any modal dialogs opened in AUT. That is, if your test stops and leaves the New Project wizard opened, the workbench context of your current test will close it
• Views - the list of all views to be opened before running the test
• Editors - the list of all editors to be opened before running the test. You can add entries to this list manually (i.e. typing in the file path, such as /my_project/my_file) or browse for existing files in workspace contexts.
• Close open editors - optionally allows to close all other editors not listed in open editors list
• Clear clipboard - optionally allows to clear clipboard contents

While it is not currently tracked by RCPTT, the Workbench context actually can depend on certain Workspace contexts. For example, you specify to open an editor for /my_project/my_file. In case there is no such file in the AUT workspace, applying this Workbench context will fail your test. When you are using workspace contexts and workbench contexts simultaneously (which is actually the recommended way), make sure that the workspace context goes before the workbench context. Alternatively, unnecessary editors can be manually removed from the list of editors.