anchor.diff:  - _contexts_, for example `{x : 5, y : 3}`;
   - _ranges_ and _lists_, for example `[1 .. 10]` or `[2, 3, 4, 5]`.
   
  -A quick overview of the supported syntax is also available in the *Scenario Cheatsheet* tab of the *Test Tools* panel on the right side of the editor.
  +A quick overview of the supported syntax is also available in the *Scenario Cheatsheet* tab of the *Test Tools* panel on the right side of the designer.
   
   === Lists and Maps
   
  
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: 
  === Running a Test Scenario in Business Central
  
  Click *Run Test* at the top of the Test Scenarios designer.
  The *Test Report* tab automatically opens on the right with the test results; a red cross indicates test failures whereas a green check mark indicates that all tests were successful.
  
  In the panel, information regarding the overall test status, time of completion, number of run scenarios, and duration is displayed.
  
  To view a table with detailed failures stack traces, click *View Alerts*.
  The *Alerts* panel at the bottom of the designer opens.
  
  .Reporting panel
  image::Workbench/AuthoringAssets/sc4.png[align="center"]
  