anchor.diff:  [[_drools.testscenarioprevieweditor]]
   = Test Scenarios
   
  -The aim of the new _Test Scenarios_ editor is to help the user test the proper function of created rules and knowledge bases.
  -Compared with the current Test Scenarios (Legacy) editor, the new version is significantly enhanced by an improved user experience that introduces a tabular layout, which guides the user during the definition of a scenario template and all the assorted test cases.
  +The aim of the new _Test Scenarios_ designer is to help the user test the proper function of created rules and knowledge bases.
  +Compared with the current Test Scenarios (Legacy) designer, the new version is significantly enhanced by an improved user experience that introduces a tabular layout, which guides the user during the definition of a scenario template and all the assorted test cases.
   Running the defined scenarios verifies that the system works as expected and does not contain any regressions after a change.
   A considerable improvement is the full support of DMN model testing.
   
  -.Test Scenarios editor
  +.Test Scenarios designer
   image::Workbench/AuthoringAssets/sc1.png[align="center"]
   
  -The editor's layout consists of a table, which contains a header and individual rows.
  +The designer's layout consists of a table, which contains a header and individual rows.
   The header (test scenario template) is divided into two parts; the *given* data object fields, which represent the input information, and the *expected* data object fields, whose values are checked based on the given information and which constitute the expected result.
   The rows (test scenario definitions) represent the separate test cases.
   
  -An integral part of the editor is the right panel, which can be used for configuring the data object mappings, for accessing the cheat sheet that contains a set of notes used for quick reference, and for displaying the tests results in the *Test Report* tab.
  -
  -WARNING: Currently, the editor can only use the default KIE session.
  +An integral part of the designer is the right panel, which can be used for configuring the data object mappings, for accessing the cheat sheet that contains a set of notes used for quick reference, and for displaying the tests results in the *Test Report* tab.
  +
  +WARNING: Currently, the designer can only use the default KIE session.
   
   NOTE: Some features described below are available only for rule-based test scenario assets, whereas others only for DMN-based scenarios.
   If applicable, the difference is indicated in the title of a corresponding part of the document.
  
positive.code: . Enter a name of the test scenario and select a package.
  . Specify the source type; a test scenario can either be rule-based or DMN-based.
  If the source type is a DMN file, make sure the file is available in the project and select the file from the *Choose DMN asset* picker.
  . Click *Ok* to create the asset and open the editor.
  
  All test scenarios are files with the `.scesim` file name extension.
  
  
negative.code: In the panel, it is possible to search the data objects using the *Search* text box. To search data object, start typing the name (or any part of the name) and press *Enter* or click the search button.
  
  To load a data object that is located in a different package than the opened test scenario, the data object must be imported first.
  To import a data object, select the *Data Objects* tab directly in the designer, click *New item* and in the *Add Import* dialog window, choose the data object from the drop-down list and click *Ok*.
  After you save, close, and reopen the test scenario, the added data object from a different package will be displayed in the list of all available data objects.
  
  === Basic Interaction Using the Contextual Menu
  