I have been using Sahi Pro from 2016. The scripts that you develop using this tool is very stable. Whenever i have faced an issue the customer support has been so helpful and solve the issue within few days of time. I have used Sahi Pro Web for various web applications. Recently tried out the desktop add-on and it works very well too. May be in future i will try the Mobile add-on if the need arises.

Sahi Pro is a user friendly tool. Non automation testers or beginners can easily use the tool. The documentation covers most of the topics (usage, issues you may face, integration with other tools etc.) Not to forget the constant customer support they provide even during the trial period. This tool is fantastic and is affordable. I have mostly interacted with the rep from Sahi Pro. Must say he is so knowledged, so quick and solves all the issues so patiently.

May be the look and feel of the tool can be improved.

Developing a quick feedback system for making confident code commits and reducing defect leakage are the key business problems we are trying to solve. Sahi helps as it has fast development cycle, easy to setup framework and strong fault-tolerant recognition capabilities.

Test automation ease is based on out of the box framework components like fault tolerant recognition parameters, reporting and exception handling . Relational operators in sahi provide easy to write DOM recognition parameters. Moreover these are not brittle like XPATH recognition strings. Reporting and exception handling is built into the framework. That provides a quick system in place to start test automation with minimal setup. Unlike other frameworks where in various components need to be in place before one can actually start putting in test automation. ROI in test automation frameworks is long term. And it is realized only when automated tests start catching bugs. Initial framework building time gets cuts down in case of SAHI and hence time for ROI realization gets cut down.

Maintenance is a big overhead for any test automation project. Hence debugging capabilities greatly help cut down maintenance effort. There is scope for improvement in case of debugging capabilities. Here are some areas which can be improved in the software. (1) For large scale test automation, amount of time it takes to analyze a failing script and conclude if it is a false alarm can be cut down. Common interaction/recognition failures can be rolled up at suite level. This will help summarize total failing constructs. This debugging info is present at the script level today (2) Just like snapshot capturing, if there can be video capturing of playback, it will greatly help understanding behavior of application under test, test environment and the test automation tool when put for un-attended schedules. One can still setup a desktop recorder in absence of the same. But a tool capability provides way to turn on such debugging only in cases where it is not easy to debug why certain scripts fail in an un-attended run. (3) Heuristic analysis on consistent failing scripts, suites and similar insights should provide quick correction mechanism for reducing waste in the system. There is already suite level playback information stored in the SAHI DB. That data can be analyzed for heuristic/predictive analysis providing recommendations and corrections in overall test automation system. Currently there is only suite level pass/fail information.

Cut down the overall testing effort by automation mundane UI validation effort like smoke and regression. Were able to significantly cost of testing as well help in deploying faster into production.

- Ease of installation and lightweight - Easy to train QA on SahiPro with in-built 1000+ API which helps to augment faster automation - Integration with DevOps pipeline along with the ability to distribute the test script efficiently thru' master/slave - Regular enhancement on the tools

- Absence of an online community to solve the frequent issue. Will be good to be active on StackOverflow - Turn around time for support some time exceed three days with back and forth email - Recently, the cost of procuring additional add-on is not well received. I wish, it is one package cost

What we do : - Daily Regression Tests (run with Jenkins) - Regression Tests when Developper Team deliver new application version - Use on 5-10 applications

Many features and API Good documentation Easy to code Easy to integrate with continus integration

Price is growing every Year We had some problems on country setting (time format, decimal separator, ...) I would like more guidelines to help build Global Regression tests for an application (how to organize Data Set, how to buil tests code architecture, ...)

We are using Sahi Pro for automating End to End business process scenarios and it helps us really to identify bugs at prior stage.

Easy to understand and Train people. No Programming knowledge required. User Friendly UI Easy Integration with CI tools.

No cons such as! Should add specific apis related to Load testing.