Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Papyrus/Tester/RCPTT"

(Root Structure)
(Open points)
Line 61: Line 61:
  
 
= Open points =
 
= Open points =
* Naming Convention
+
== Naming Convention ==
* Directory Structure
+
* What should be that best naming convention to make the tests structured ?
* Common Library
+
== Directory Structure ==
 +
* How deep should be the test folder
 +
== Common Library ==
 +
* How this library can be put in place (ECL, Java, ???)
 +
* What will be added into this library ?
 +
== Industrialization ==
 +
* Should we create a special Hudson job to run the RCPTT
 +
* On which version of Papyrus should be based the AUT ?
 +
* On which version of Papyrus RT should be based the AUT ?

Revision as of 11:59, 2 December 2015

Introduction

RCPTT is an Eclipse Project that provides a testing tool for Eclipse RCP application. RCPTT allows to run GUI tests based on ECL. Several functions as the "Record actions" make RCPTT easy to handle and use for beginners. After a bit of experience, it will be easy to understand the different command and make the scripts lighter.

The RCPTT "framwork" has been put in place in Papyrus RT. Some tests are arleady created and could base as example.

How to use RCPTT

This small video shows how to create a test for papyrus RT: http://www.papyrus-support.com/rcptt-with-papyrus-real-time/

RCPTT Eclipse can be found here

Good Practices

Here are some tips to have an homogeneous practice around RCPTT. This is a certain way to work, maybe not the best one. If you have other opinion, please share it here.

Root Structure

In the rcptt root in org.eclipse.papyrus-rt\releng\rcptt of the project we should have :

FolderAtRoot.JPG

Folder Structure

After importing the rcptt folder into the RCPTT eclipse IDE, the the tests created should respect architecture to make this folder easy to maintain.

ImportedFolderStructure.JPG

Project Properties file

rcptt.properties is shown as Project Settings file in the Test Explorer and contains Description, default contexts and default Validations.

Contexts

There are several type of contexts :

  • Preferences contexts
    • Like the UMLRTViewPoint
  • Workbenchs contexts
    • For exemple: Perspective to use
  • Workspaces contexts
    • For example clear the workspace
    • Inital project to be used for the further test
  • Procedures contexts
    • ECL Procedures that will be used as common library for RCPTT test

Naming Convention

Contexts Name

In order to quickly identify a Context file, the context name should be prefixed with the string "CTX_".

CTX_[ContextName]

For example:

CTX_UMLRTViewPoint

Test Name

All tests are executed alphabetically and this should work as each test must be independant ! But in order to have a better overview during execution, it would be a good practice to regroup test by feature. For this reason here is a naming convention used as for now:

[FeatureName]_[XY]_[TestName]
  • X = Type of the test (e.i.: 0: initialisation, 1: creation, 2: deletion, 3: modification , ...)
  • Y = Number of this test of this type X

For Example:

CallEvent_15_CreateCallEventTest

Represents a test around CallEvent, 1 = creation , 5 = fifth test of Creation of CallEvent.

Open points

Naming Convention

  • What should be that best naming convention to make the tests structured ?

Directory Structure

  • How deep should be the test folder

Common Library

  • How this library can be put in place (ECL, Java, ???)
  • What will be added into this library ?

Industrialization

  • Should we create a special Hudson job to run the RCPTT
  • On which version of Papyrus should be based the AUT ?
  • On which version of Papyrus RT should be based the AUT ?

Back to the top