What is new in Sahi Pro v9.1.2

abstract Sahi Pro v9.1.2 is a minor release with performance improvement and bug fixes.

warning

If you're installing Sahi Pro for the first time or want to install Sahi Pro v9.1.2 from installer in a new location, then please refer Sahi Pro - Getting Started page.
If you wish to upgrade from an older version of Sahi using installer, refer to Upgrade Sahi Pro for details. After upgrading to v9.1.2, follow the instructions below.
1. Add following patterns to 'SahiBaseDir\userdata\config\donot_download_urls.txt'.
  - .*threatListUpdates.*
  - .*chrome-variations\/seed.*
  - .*edgedl.*
  - .*openh264[.]org.*
2. Open 'SahiBaseDir\userdata\config\browser_types.xml'. Append below line to options element in browser types for 'chrome' and 'edgenew'.
  - --disable-renderer-backgrounding --disable-background-networking --disable-component-update

warning

If you are using Sahi Pro v9.0.1 or above version, you can easily update to Sahi Pro v9.1.2 through Update Sahi Pro web UI.
For updating from Sahi Pro v9.0.0, please follow the instructions below.

On Linux OS, after upgrading through Update Sahi Pro web UI please grant permission for the 'SahiBaseDir/userdata/bin/verify_ssl_root_cert_linux.sh' file.
Eg: chmod 755 verify_ssl_root_cert_linux.sh
On Windows OS, when using any DB apart from H2, the Update feature stops working.
You need to update at least once from Sahi Pro 9.0.0 version in this manner to ensure all future updates work fine.

Resolution:
You will need to temporarily switch your database to H2 > Perform the Update and then Switch back to your current database settings.
For more information about using different databases for reports please see the document for Use a Different Database in Using Sahi.

Steps:
1. Take a backup of your existing database. (It may be "mysql", "mssql", "postgresql", "oracle" etc.) When upgrading Sahi Pro and reverting your database back to your current one, your db will also get updated. So, in order to avoid losing any data, taking a backup is a must before proceeding to the below steps.
2. Switch your database settings to H2 database.
3. Perform update through Update Sahi Pro web UI.
4. Now Switch back to your original DB settings.

Performance improvements in Sahi Playback
- During playback, it is necessary to identify inactive browser windows. Earlier a separate thread was created per browser session for this activity. Now, a single thread will suffice for all the browser sessions.
- Optimized processing of HTTP requests.
- Cached and reused regex patterns.
- Avoided downloading browser and system updates to Sahi's download directory.
Introduced property testcase.restart_browser_if_aborted to restart the browser for an aborted test case in a scenario file during playback.
Introduced property drun.auto_rerun_scripts_if_internal_aborted to configure re-execution of the script if communication between Sahi Master and node is lost while the execution is in progress. If the property is enabled Script will be set to INTERNAL_ABORTED_RETRY status and will try to execute again. If the property is disabled, Script will be set to INTERNAL_ABORTED status.
Improvement in _dragDrop API to support drag-drop better.
Fixed: Issue in ping from IE8 browser.
Fixed: Issue in JS code coverage for ECMAScript 6 code(Partial fix).
Fixed: Base window gets identified as a popup in Firefox version 86 when navigated to a different domain.
Fixed: Issue occurs in identifying a popup after the latest browser update.
Fixed: Issue occurs in _closeWindow API after the latest browser update.

_dragDrop: In versions before Sahi v9.1.0, _dragDrop API would drag from the top left of draggable and drop at the top left of droppable. However in few applications, this top-left position did not facilitate drag-drop operation. So in v9.1.0, _dragDrop API was improved and it dragged from the center of draggable and dropped at the center of droppable. But using center position caused a few existing _dragDrop API statements to fail. To support such _dragDrop API statements written in versions before v9.1.0, the following changes have been introduced for _dragDrop API in v9.1.2 :
- By default, _dragDrop API would use the center position. If any _dragDrop API statement has _xy API for the drag/drop element, then the top-left position will be used for that drag-drop statement.
- A new property sahi.browser.dragdrop.top_left is introduced in userdata.properties with default value as false. If this property is set as true, then the top-left position will be used for ALL drag-drop operations.

Windows Application: Fixed a bug in identifying elements for systems having display language as Turkish.