18 January 2026:
Sahi Pro is an enterprise grade test automation platform which can automate web, mobile, API, windows and java based applications and SAP.
This forum is now archived and is in read-only mode. Please continue discussions on our improved new Sahi Pro Community forum.
Sahi Pro is an enterprise grade test automation platform which can automate web, mobile, API, windows and java based applications and SAP.
My experience using Sahi
I am relatively new to Sahi. I came to know about Sahi 3 months back and used successfully in one of our testing projects. Let me list down the features of Sahi that impressed me
• Minimum learning curve. Though I have no experience in JavaScript, I was up and running in 2 days time and was able to bring a team on their own in less than a week. I do not think something of this sort is achievable with any other test automation tool.
• Tiny, cute, all-in-one package. Includes a proxy based recorder, very useful object-inspector, easy to use built-in debugger that helps in testing your code snippets, test execution and color coded html logs.
• Setup once and use from any where: Once the proxy server is up, Sahi is accessible using a browser to record scripts, debug statements, execute tests and view logs. All that is required is to configure the proxy settings of the browser.
• Browser independence: We tested all our scripts both on IE and FireFox. Saved good amount of time.
• Parallel execution of independent tests reduces the overall testing time. Most of our scripts had to be executed on 4 variants of the application on both IE and FireFox!
• Reading from and writing to Excel is easy: Helped a lot in data driving our tests.
• Modern style exception handling is very powerful
• Client side extensibility is a nice cool feature.
• Ant/batch integration helps to integrate testing into the build process. (I have not used this feature as we trigger the execution from browser, for the time being)
Let me brief areas where I had difficulty while using Sahi.
• I faced difficulty in catching up with the concept of _set and _condition. The usage of these APIs is well documented, but since Sahi was so easy to learn, I skipped reading them!!
• Modifying the script after recording: Since everything that I wanted was available in the Sahi controller, I was searching for an editor page where I can open, modify and save my existing scripts. I spent some time looking for it but could not locate one. And that is the first item in my Sahi wish list: A simple text editor accessible over browser.
That is it about my 2 months of experience using Sahi. And my best wishes to Sahi, Narayan and the Sahi community
• Minimum learning curve. Though I have no experience in JavaScript, I was up and running in 2 days time and was able to bring a team on their own in less than a week. I do not think something of this sort is achievable with any other test automation tool.
• Tiny, cute, all-in-one package. Includes a proxy based recorder, very useful object-inspector, easy to use built-in debugger that helps in testing your code snippets, test execution and color coded html logs.
• Setup once and use from any where: Once the proxy server is up, Sahi is accessible using a browser to record scripts, debug statements, execute tests and view logs. All that is required is to configure the proxy settings of the browser.
• Browser independence: We tested all our scripts both on IE and FireFox. Saved good amount of time.
• Parallel execution of independent tests reduces the overall testing time. Most of our scripts had to be executed on 4 variants of the application on both IE and FireFox!
• Reading from and writing to Excel is easy: Helped a lot in data driving our tests.
• Modern style exception handling is very powerful
• Client side extensibility is a nice cool feature.
• Ant/batch integration helps to integrate testing into the build process. (I have not used this feature as we trigger the execution from browser, for the time being)
Let me brief areas where I had difficulty while using Sahi.
• I faced difficulty in catching up with the concept of _set and _condition. The usage of these APIs is well documented, but since Sahi was so easy to learn, I skipped reading them!!
• Modifying the script after recording: Since everything that I wanted was available in the Sahi controller, I was searching for an editor page where I can open, modify and save my existing scripts. I spent some time looking for it but could not locate one. And that is the first item in my Sahi wish list: A simple text editor accessible over browser.
That is it about my 2 months of experience using Sahi. And my best wishes to Sahi, Narayan and the Sahi community
This discussion has been closed.