Blog

Latest Updates. News. Insights. Ideas.

February 2017 - Sahi Pro

Sahi Pro is sponsoring Agile Testing Days Asia and Agile India conference

Posted by | Agile India, Agile Testing Days, Conferences | No Comments

SahiPro_Conferences_MarchSahi Pro is happy to sponsor two conferences this quarter. We would love to meet you at the conference.

Agile Testing Days Asia – http://agiletestingdays.asia/
March 01 – 03, 2017
Bangalore, India
Buy Tickets

Agile India 2017http://2017.agileindia.org/
March 05 – 12, 2017
Bangalore, India
Buy Tickets

Do email us and we will share the 15% discount code to you and your team members.
Email id: info [AT] sahipro [AT] com

Sahi Pro: Troubleshooting Series: Remote Desktop Connection (RDC)

Posted by | technical, troubleshooting | No Comments

Last week, we saw how to troubleshoot SSL issues.
Similarly, during automation, one might have to do a remote desktop connection (RDC) to multiple machines and there are chances of minimizing or closing the RDC connections. In this blog post, we discuss the solutions to problems with native elements if the RDC is minimised or closed.

Scenario 1: Minimised Remote Desktop Connection
When tests are executed on a remote machine using Remote Desktop Connection and the RDC window remains minimised, native events (including taking screenshots) fail to work.
To fix this, one needs to add registry keys on the client machine from which the Remote Desktop Connection is made.
NOTE that these keys are to be modified on the client and not the remote machine.

Please be careful while changing the registry entries.

Registry Editor

  • Launch the Windows Registry as appropriate on your Windows machine
  • For 32-bit Windows, find the registry key:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Terminal Server Client
  • For 64 bit Windows, find the registry key:
    HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Terminal Server Client
  • Create a DWORD value with the name RemoteDesktop_SuppressWhenMinimized with value 2.
  • Run the tests.

Now native events should work well with a minimised Remote Desktop Connection.

Scenario 2: Closed Remote Desktop Connection
Sometimes users would want to open a Remote Desktop Connection, start running the tests on the remote machine, and close off the connection from the client while the tests are running.
In this case, native events (including taking screenshots) fail to work.

To work around this, please do the following instead of closing the remote desktop connection directly.

  • Create a batch file on the Remote machine’s Desktop (For example: “disconnect.bat”).
  • Type the following line in the file –
    tscon %sessionname% /dest:console
    and save it.
  • Start off the tests on the Remote machine.
  • Do not close the Remote Desktop Connection from the client directly.
  • Instead, double click on the batch file. The session will be closed by the remote desktop.

    Now native events should work well with the closed Remote Desktop Connection.

Scenario 3: Right Click > Paste (Clipboard) missing in RDP (RDC)

Clipboard Checked

Even though you have ensured that Clipboard is checked and available during the remote session, when you do a right click after a copy, the paste option might be disabled.

All you need to do is to kill the clipboard process and restart it again! You can do so by running the following command from the windows run command (Windows Key + R) or cmd (on the remote machine):

Taskkill.exe /im rdpclip.exe

The command above will kill RDP Clip Monitor process, and then you can restart the process again by running the following command:

Rdpclip.exe

It should start the process again and the clipboard should start working again now

Refer the following link for more information:
https://www.svenbit.com/2014/11/restart-copy-and-paste-clipboard-functionality-in-rdp/

Hope this post gave you information about troubleshooting RDC issues. Feel free to let us know if you face any other issues by sending an email to support [AT] sahipro [DOT] com

We will cover those in the upcoming posts.

Five Questions Series: Sahi Pro Licensing: User License vs Concurrent License

Posted by | License | No Comments

In the fifth post on the Five Questions Series, we have Sahi Pro Pricing and Licensing today.
Previous posts in this series: Sahi Relational APIsSahi Controller, Sahi Logs and Sahi Excel Framework.

Sahi_Pricing_And_Licensing

What is the pricing model of Sahi Pro?
There are two types of licenses for Sahi Pro – User License and Concurrent License.
Global usage license:
User License costs 695 USD and Concurrent License costs 995 USD.
India only usage license:
User License costs INR 31275 plus taxes and Concurrent License costs INR 44775 plus taxes
To purchase Global usage license in INR, please email sales [AT] sahipro [DOT] com

What is the difference between a user license and a concurrent license?
Sahi Pro USER License (recommended for smaller testing teams)

Sahi Pro USER licenses are based on number of users creating and maintaining Sahi scripts.
With the purchase of a single USER license, a single tester can

  • Install Sahi Pro on multiple machines for developing scripts with the same license (for example, develop scripts on a Mac, Windows with IE8 and Windows with IE11).
  • Install Sahi Pro Runner on multiple machines for playback of scripts with the same license (for example, with build farms or Continuous Integration systems).
    Sahi Pro licenses are based on number of users creating and maintaining Sahi scripts.
    If you have a 5 member testing team, you will need to buy 5 licenses.
    The testers can install their licenses on multiple machines for script development and maintenance.

Sahi Pro CONCURRENT License (recommended for enterprises)
Sahi Pro Concurrent license allows multiple team members to use a pool of licenses. If you have a team of 15 members of which any 10 users may be using Sahi Pro at any time, you can buy 10 Concurrent licenses. As long as the total count of concurrent users is less than or equal to 10, any user in the organization can use that license. The license is not tied to a specific user.
License server is available in the download archives page.
Any number of Sahi Pro Runner instances can be run using the concurrent license (for example, with build farms or Continuous Integration systems). Sahi Pro Runner instances do not contribute to the count of concurrent users.

Do I need to pay separately for the Sahi Pro Runner? Sahi_Pro_Runner
Sahi Pro Runner uses the same license as Sahi Pro.
If you own a Sahi Pro license, you can download and use Sahi Pro Runner with the same license on multiple machines. Both Sahi Pro and Sahi Pro Runner need to be on the same version.

What happens after the license expires?
The License will still be active but the support and upgrades will not be available.
Sahi Pro License is subscription based license which needs to be renewed every year to get continuous support and upgrades.

If I want to manage my licenses, do you offer any support?
Yes, we offer complete support. We provide license server to manage concurrent license.

Any other questions in your mind?
Feel free to comment or ask your question(s) and we will get back to you.

SahiPro Troubleshooting Series: SSL Issues

Posted by | technical, troubleshooting | No Comments

We take pride in helping our customers solve their automation issues. We are planning to come up with a list of commonly faced issues and how we solved it. This might help multiple customers when they face similar issues. Over a period of time, this would turn into a good repository of problems and solutions.

Today, we share the common problems faced by our customers with SSL

Issue 1: Certificates does not conform to algorithm constraints
Certificates does not conform to algorithm constraints

Sahi Pro Console Error

javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Ce
rtificates does not conform to algorithm constraints
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.SSLSocketImpl.fatal(Unknown Source)
at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown Source)
at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source)
at sun.security.ssl.Handshaker.processLoop(Unknown Source)
at sun.security.ssl.Handshaker.process_record(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source
)

Solution:
Please perform all the steps highlighted below:
  • Open C:\Program Files\Java\jre1.8.0_111\lib\security\java.security file.
    The above path is for jre version 1.8.0_111. In your case, it might be different.
  • Search for the lines
    jdk.certpath.disabledAlgorithms=
    jdk.tls.disabledAlgorithms=
    jdk.jar.disabledAlgorithms=
    and comment them by prefixing # such that they look like this:
    #jdk.certpath.disabledAlgorithms=
    #jdk.tls.disabledAlgorithms=
    #jdk.jar.disabledAlgorithms= 
  • Open <SahiPro>/bin/dashboard.bat file and modify below lines fromjava -Djsse.enableSNIExtension=true -Djava.util.logging.config.file=%SAHI_USERDATA_DIR_TMP%\config\log.properties -classpath %SAHI_EXT_CLASS_PATH%;%SAHI_CLASS_PATH% net.sf.sahi.ui.Dashboard “%SAHI_HOME%” “%SAHI_USERDATA_DIR_TMP%”
    to
    java -Djsse.enableSNIExtension=true -Dhttps.protocols=SSLv2Hello,TLSv1,TLSv1.1 -Djava.util.logging.config.file=%SAHI_USERDATA_DIR_TMP%\config\log.properties -classpath %SAHI_EXT_CLASS_PATH%;%SAHI_CLASS_PATH% net.sf.sahi.ui.Dashboard “%SAHI_HOME%” “%SAHI_USERDATA_DIR_TMP%”
  • Save the changes and restart Sahi Pro.

Issue 2: “ERR_SSL_VERSION_OR_CIPHER_MISMATCH”
SSL_VERSION

Solution:

  • Please modify the following property in <SahiPro>/bin/dashboard.bat by toggling the value from true to false or false to true.
    -Djsse.enableSNIExtension=true
    or
    -Djsse.enableSNIExtension=false
  • Save the changes and restart Sahi Pro.

Issue 3: ERR_SSL_PROTOCOL_ERROR
Protocol
Solution:

  • Take a back up of <SahiPro>/bin/dashboard.bat and modify the following fromjava -Djsse.enableSNIExtension=true -Djava.util.logging.config.file=%SAHI_USERDATA_DIR_TMP%\config\log.properties -classpath %SAHI_EXT_CLASS_PATH%;%SAHI_CLASS_PATH% net.sf.sahi.ui.Dashboard “%SAHI_HOME%” “%SAHI_USERDATA_DIR_TMP%”
    to
    java -Djsse.enableSNIExtension=true -Dhttps.protocols=”SSLv3,SSLv2Hello,TLSv1″ -Djava.util.logging.config.file=%SAHI_USERDATA_DIR_TMP%\config\log.properties -classpath %SAHI_EXT_CLASS_PATH%;%SAHI_CLASS_PATH% net.sf.sahi.ui.Dashboard “%SAHI_HOME%” “%SAHI_USERDATA_DIR_TMP%”
  • Save the changes and restart Sahi Pro.

    Hope this post gave you information about troubleshooting SSL issues. Feel free to let us know if you face any other issues by sending an email to support [AT] sahipro [DOT] comWe will cover those in the upcoming posts.

Use fully-loaded Sahi Pro FREE for a month. Download Now Request a Demo