Skip to main content
Jump to: navigation, search

EASE/UnitTest/UI/TestSuiteEditor

Introduction

  • This page contains a user guide for users that intend to use the Test Suite Editor and the Script Unit Test components in the EASE Unit Testing Framework.
  • It addresses any interested party that wants to make use of the EASE Scripting Unit Testing Framework.

General Concepts

  • The Test Suite Editor window allows the user to implement the tests in a configurable way, and to run them, see the figure below for a screenshot example of this window:

ScreenshotTestSuiteEditor.PNG

  • The Script Unit Test window allows the user to visualize the summary of results after the tests are run, see the figure below for a screenshot example of this window:

ScreenshotScriptUnitTest.PNG

  • The Test Suite Editor is an UI window that contains several pages, and which allows the user to create, to modify and to monitor the tests.
  • The EASE Scripting Unit Testing Framework uses the following basic concepts for implementing and running a test instance:
    • A test is composed of several test cases.
    • Each test (also called test suite) is defined by a (Script) Test Suite instance.
    • Each test case (also called test) is defined by a JavaScript Source File.
      • So, each (Script) Test Suite instance contains one or more JavaScript Source File instances.
      • And consequently, for writing the test cases, the JavaScript syntax is used.
    • Each (Script) Test Suite instance can be modified and monitored by using the Test Suite Editor window.
  • The Test Suite Editor window contains the following main pages:
    • Components: allowing to select the tests that are to be run.
    • Description: containing a description of the test.
    • Variables: allowing to define input configuration parameters as variables for the test, see the figure below for a screenshot example of this page:

ScreenshotVariablesEditor.PNG

    • Variables: allowing to categorize variables in groups, see the figure below for a screenshot example of this page:

VariablesGroupedTree.png

    • Setup: allowing to setup the test.
    • Source: containing the internal source code of the "Test Suite" instance in XML format.

Prerequisites

  • You will need to install at least EASE v0.2.0 to be able to use this feature.

Getting Started

  1. Create a java project.
  2. Add a script test suite to your project.
  3. Add a java script source file to your project to define your test case (this step can be repeated every time a new test case is added to the test).
  4. Following the previous step, the corresponding TestSuite editor window will be created.
    1. Examples of some basic events to perform in the TestSuite editor window are:
      1. Open the java script source file corresponding to the test case and alter it as required.
      2. Click Variables to define the configuration parameters for the test.
      3. Click Setup to setup the test.
      4. Click Components to select the test cases that are to be run and click Run to actually run them.
    2. Open the Script Unit Test window to visualize the summary of results after the selected tests were run.

Detailed Concepts

  • For a summary of the detailed concepts concerning the Test Suite Editor and the Script Unit Test components, see the figure below:

GeneralConcepts.png

Script Unit Test Window

  • Script Unit Test window allows the user to monitor the results and the summary of the tests defined for a test suite.
  • Script Unit Test window contains four main areas, as visualized in the figure below:

ScriptUnitEditorWindow.png

Test Suite Editor Window

Preliminaries

  • Test Suite Editor window allows to implement the test defined for a specific test suite.
  • Any test suite can contain as many tests as needed.
  • Test Suite Editor window contains the following page editors (with corresponding purposes for each editor), as visualized in the figure below:

TestSuiteEditorWindow.png

Main Pages

Variables
  • Variables editor window allows definition of configuration parameters as variables for the test cases contained in the test suite instance.
  • Variables editor window comprises three columns, i.e. variable, content, and description columns.
  • The variables can be categorized in groups.
  • All the elements of the window are contained in a tree data structure.
  • Groups and variables are created via a context menu, which allows:
    • to add groups to the currently selected group in the tree.
    • to add sibling groups to the currently selected group or variable in the tree.
    • to add variables to the currently selected group in the tree.
    • to remove any selected element from the tree.
  • Any entity in the tree can be dragged and dropped in the corresponding group.
  • Drag and drop is supported for generic entities defined in the Variables editor window.
  • Drag and drop is supported for multiple selected entities in the Variables editor window.
  • Any entity in the Variables editor window can be renamed by double clicking the entity itself and inserting the new name.
  • For a summary of the Variables editor window see the figure below:

VariablesEditorUpdated.png

Troubleshooting

  • If errors occur and they cannot be tracked and solved by the error log messages, they should be reported as Bugzilla issues to the responsible party.

Back to the top