Worksoft Certify Reviews

I primarily used the platform for SAP projects.

From a functional perspective, I found all the solution features quite useful. Excel automation was a valuable feature that was much more efficient than working with record sets. Using it helped significantly reduce time when dealing with large datasets. 

Another standout feature is the ease with which a non-coding professional can be trained to use it for automation. The codeless automation feature, especially for SAP applications, made the process simpler and more efficient.

The product could be improved in terms of web applications. One challenge I faced was that web application parameters often change in the back end, affecting the automation scripts. Small changes in the HTML page design can impact the automation process, unlike SAP, where the script remains stable unless there is a functional change. Therefore, maintaining automation for web applications requires more effort.

If my script is long and involves a large data set with over a hundred entries, it can slow down or become inefficient. I suggest improving how the platform handles large datasets during lengthy scripts.

I have worked with Worksoft Certify for over five years.

Worksoft Certify has good integration capabilities with third-party tools. For instance, I successfully integrated it with Excel and PDF. Although I haven't used the mobile features, it supports desktop applications well. In my projects, especially SAP, it handled invoicing and PDF verifications seamlessly. 

It is a codeless automation tool. It allows even freshers to be trained and become productive within a month. Regarding project cost, having a senior resource oversee the automation is feasible, while junior resources can handle the bulk of the work. Although it is a licensed product, it significantly saves time and effort, especially with its internal tools that allow testers to capture and automate steps efficiently.

Overall, I rate it a six out of ten. 

We use the solution in pharmacy and retail.

We focus on automation solutions for SAP, Oracle, and Salesforce. Worksoft Certify is developed and designed to support these platforms. It matches what we want to achieve, providing capabilities in process mining and generating process documentation from these cases. Additionally, it can create RPA bots to execute tasks in production, making it a meaningful tool.

Worksoft developed a tool to support ERP testing. All prebuilt functions are good at steering the application when the test is executed.

Some features are missing from a testing perspective. You need to know how to connect everything to create requirements and stability metrics for the routine.

I rate the solution’s stability a seven out of ten.

You can scale it as you want. Just install it properly. It is suitable for enterprise customers.

I rate the solution’s scalability a ten out of ten.

The initial setup is easy and can be completed in two days. The team provided good support. 

I rate the initial setup a nine out of ten, where one is difficult, and ten is easy. 

They conducted marketing research through some external agencies, which reported an ROI of 583% over a five-year period. This is quite significant. You don't need people to edit test cases manually; instead, it creates and runs tests automatically whenever you wish, even after working hours or at any time.

The tool is worth the money.

The usability of test cases and running tests overnight is a definite advantage of Worksoft Certify. This provides great visibility into the process. One notable feature of Worksoft Certify is its support for SAP migration. For example, it fully supports SAP migrations. Many customers use ECC, which is becoming a legacy and must migrate to SAP S/4HANA. You can create your test cases in ECC and run them later in S/4HANA. It saves a lot of time. Additionally, you can perform parallel testing to ensure that the new functionality implemented in S/4HANA matches the legacy system.

I recommend Worksoft Certify because of its stability. The company has been in business for almost thirty years, maintaining the same customer base. They have a substantial portfolio and extensive experience, contributing to their reliability and effectiveness.

Overall, I rate the solution a nine out of ten.

I use Worksoft Certify primarily for the functional testing of SAP applications.

I run Worksoft Certify for the entire end-to-end process flow to ensure that it is always working before and after patch upgrades, release upgrades, or any changes to the system when I run the test script.

My company gets some savings in manpower and cost and enjoys a boost in productivity because you only need a few hours to run end-to-end testing using the tool. If you do it manually, the process takes a few weeks, so Worksoft Certify greatly benefits my company.

What I like about Worksoft Certify is that end-to-end testing becomes faster.

The problem with Worksoft Certify is that it's not always stable. It runs on a live platform that's constantly changing, so the test script needs to be adjusted every time, which is very painful. That's the pain point in Worksoft Certify, and if Worksoft could make the solution more stable and more "change-proof," that would help my company greatly.

A feature I want to see in Worksoft Certify is for it to be able to work on test cases on mobile devices, though that could be difficult. I also wish to have more portability in the solution in terms of the script because, in the SAP environment, my company has to run Worksoft Certify in more than one system, so if Worksoft can make the process more portable, than would be fantastic.

I've been working with Worksoft Certify for about four years now.

Worksoft Certify could be more stable. It has stability issues.

Scalability is closely linked to stability. If Worksoft Certify is stable, then it's easily scalable, and if it's not stable, then it's still scalable, but every time, you have to make some adjustments.

I'm working with Worksoft Certify.

I always work with the latest version of the solution.

My rating for Worksoft Certify is eight out of ten.

We have done one POC (proof of concept) for Worksoft Certify, for one application, for one of our clients. The POC was successful, so we implemented the solution. We did it for a pharmaceutical product, a pharmaceutical domain.

What I found most valuable in Worksoft Certify is its identification feature. I also found its automation feature valuable.

What could be improved in Worksoft Certify is its integration with other tools, for example, test management tools such as Jira, ALM, or any other test management tools. That integration is missing.

I've used Worksoft Certify for two years, and I've used it in the last twelve months.

Worksoft Certify is a stable solution. I'm rating it a four out of five in terms of stability.

Worksoft Certify is scalable, and I'm giving its stability a rating of four out of five.

The technical support for Worksoft Certify was really impressive. It was really good. We needed to create new controls, and we got a good response from their team. On a scale of one to five, with one being the worst and five being the best, I'm rating them a five.

The initial setup for Worksoft Certify was very simple. On a scale of one to five, with five being the best and one being the worst, I'm giving the initial setup a five.

Deploying Worksoft Certify took just one hour after getting the license. The implementation was done by our in-house team.

I'm not aware of any licensing costs for Worksoft Certify.

Worksoft Certify is in hybrid mode in terms of deployment.

Currently, there are 50 users of Worksoft Certify in the company.

My rating for Worksoft Certify is ten out of ten.

We use this solution for functional testing and end to end regression testing.

One of the biggest advantages for this solution is codeless automation. Because it is codeless, you can train people within a couple of hours.

The overall speed and performance of this solution could be improved. In a future release, it would be useful to be able to do API testing. 

I have used this solution for one and a half years.

The stability of this solution could be improved. 

This is a scalable solution. 

The first line support of this solution are not that knowledgeable. They do not know the products well. They have knowledge of common issues and provide a check list they want you to perform. If the issue reoccurs, they contact another layer of technical support and this is really good. 

Neutral

The initial setup of this solution was straightforward as long as you have the SQL database up and running. It is a quick setup. 

This solution is expensive. 

I would rate this solution a seven out of ten. 

It is used for codeless automation. I am using its most recent version, and it is on-premises, but we are using it through some virtual machines. It is installed on some virtual machines, and by accessing those virtual machines, we're using Worksoft Certify.

It is codeless. Typically, you have to write code in Java, Python, or another language to automate web applications or ERP applications, but Worksoft Certify is completely different. You do not need to do any coding, and you do not need to know any coding language for automation. It is completely a techno-functional tool. You can just enable the application that you want and start automating. 

There are certain tools in the market for writing the code, but they are not supported with some of the ERP solutions available, such as SAP, Oracle, etc. Worksoft Certify is not like that. It supports each and every ERP solution available in the market.

An organization doesn't need to hire new people for automation. For example, if you already have people who are well versed in SAP, you can just train them on this particular tool, and they'll be able to do automation for you. You do not need to hire any new resources for this particular tool, and even if you are hiring, you would need a less number of people. It saves costs in terms of resources. 

Scheduling and lights-out testing are very easy. You can schedule any number of test cases on a recurring or on-demand basis. So, you can run any number of test cases. Test maintenance is very easy, and you can very easily manage all your tests, which also saves cost. So, it saves costs in terms of resources and maintenance.

The Worksoft Capture feature is most valuable. For example, if you are creating a sales order in SAP, you do not need to go to each field and do everything. You do not need to write code for each and every line. You can just turn on the Worksoft Capture feature and manually perform your actions. It will capture all manual actions, and it will give you the steps. It will write the steps for you. 

They have a scheduler in Execution Manager, but it is not customizable. Its UI needs a lot of improvement. The lights-out testing is a bit difficult with that particular tool, and it needs a lot of improvement. Of course, there are so many integration options with Worksoft for execution, but when it comes to Execution Manager, which is their own tool, there is a lot of scope for improvement.

The integration with mobile needs to be improved. Initially, they used to support certain applications, and now, they are supporting all the web applications, but with minimal knowledge, it's very difficult for any tester to automate web applications. That's where they need to improve a lot. They are already working on it. They have given additional features, and with the help of those features, you can easily automate, but they need to keep making it easier for business users who do not want to get into each and every technical aspect of it. They just want to capture the actions. It is working fine with SAP, but they have to concentrate on web applications. They also need to support Safari, as well as macOS, better.

If you keep on running it for a long time without removing unnecessary things, the load on the database increases, which impacts the performance of the tool. Sometimes, it hangs or is slow. We have faced this situation with the earlier versions, such as version 9, but in the current version, there is an improvement. The slowness has drastically reduced, but a lot of improvement is still required in this particular area.

Another negative of this tool is that its license is costly. It is a bit more expensive than other tools.

I have been using this solution for close to six years.

Its stability is very good. It is reliable.

Its scalability is very good. We are a very big organization. In my team, we have close to 14 automation engineers, but there are so many other projects where Worksoft is used. I don't know the exact number, but it would be very high. Its usage is not extensive because it is mostly being used for ERP applications. 

In my previous organization also, it was implemented for many projects.

Their support is excellent. When you raise a ticket, within a day, you get the solution. If they're not able to resolve the issue at their end, and it is on our side, they connect with us and show us what exactly is happening. They check everything. 

Its initial setup is very simple.

It was implemented in-house. We get some files that we can directly install, and that's it. We do not need to do anything other than double-clicking the given files, and it creates everything automatically.

It is costly. It is a bit more expensive than Tricentis Tosca and other tools. If they reduce its price going forward and have partnerships with other vendors, it will grow like anything.

Tricentis Tosca is a strong competitor. Worksoft Certify is more expensive than Tricentis Tosca. The solution that we use depends on a client's choice. 

In the long run, most people will prefer non-coding tools, where 0% coding is required. It is, for sure, a tool that would be useful, but there is only one hiccup. If you are executing tests multiple times, you'll have various results, such as pass, fail, etc. When you are running it for so long time, the file size on the database will keep on increasing. So, you have to keep on doing the maintenance. For example, if you need the results for 2018, you should download everything. You would need some kind of storage.

In many organizations, the managers think that if they hire one or two resources with Worksoft knowledge, they can train everyone in their team, and build a good team, but that's not going to happen in the short run. That's why I advise having two to three dedicated people to train other people and build a team. With only functional team members, it is very difficult to build a proper automation team. I have seen an automation team that wanted to train 20 people. Currently, we are training 100 people. There are three of us who are training 100 people, which doesn't work out very well. So, there should be a few dedicated people for training and implementation. 

I would rate Worksoft Certify an eight out of ten. It is a fantastic tool. Its maintenance is easy. Building test cases is easy, and planning is easy. Almost everything is easy, but the look-and-feel of the Execution Manager scheduler is not good, and currently, customization is not available, and product creation is not available.

We have an SAP application, and for the automation of this SAP application, we are using Worksoft Certify. This project is in the healthcare domain. I get the requirements from the client. They tell me about the new changes that are going to happen in the system, and based on that, we do the automation. The client tells me about the scripts and new features in the application, and I create an estimation plan, which depends on the size and the complexity of the scripts and features, and share it with the client. We do the development activities accordingly.

We have two teams. Being an automation team, we are not very much on the functional side. So, we need to take some support from the functionality team. for test case writing. They are usually able to give us steps in Excel or something like that, and we are able to start with that. Otherwise, we have some sessions with the client or the functional team to discuss any issues or doubts we have. We also need data for developing the script. We get the required information about the data, such as if data is consumable and how to find new data, from the client or the functional team. Once the automation is done, we inform the client, and we are ready for the sign-up for the first set of the script. They do a functional review, and after they okay it, we do the final sign-off. We then move our scripts from the local sandbox folder to a production folder created in Worksoft Certify. We then use the script for regression.

In terms of its deployment, they provide the updates, and we install them on our VPS.

We are mainly using it for the SAP application, and for the SAP application, if you don't have any experience with automation tools, after a few training sessions, you can easily automate the scripts. That's because no specific programming language is used. All resources that I have are specifically SAP resources. They are not from the automation background, but after gaining the knowledge, they are able to develop a script, or when there is any issue while doing regression testing, they are at least able to understand the issue, such as whether the issue is in the code or data. 

We can use it for the web application, but we are facing stability-related challenges. The properties are getting changed. For example, when I am performing any operation on the text box but the development team has done some changes, our Worksoft scripts are getting changed. This is the main challenge that we are facing while developing tests for the web application in Worksoft Certify, where any changes in the backend are indirectly impacting our scripts. For the web application, there is a scarcity of resources. Unlike an SAP application that doesn't require much experience, for the web application, you require experienced people.

We also use XF definitions for the web application, but we can't create them on our own. So, we need to take support from the Worksoft team, and we have a dependency on them.

I have been working with this tool for the last five years.

It is completely stable for our SAP application. There is no issue. Once you have developed a script, you don't need to do any changes.

We are using it on quite a large scale. If we have a requirement for the new development, we have to use Certify. My project involves maintenance and new development. In the maintenance phase, we have regression testing. We have created a batch file, and when we are doing the regression testing, we are executing this batch file. So, we are using it for day-to-day activities. We are also using another tool from Worksoft called Worksoft Execution Manager.

The number of users working on this solution varies based on the project timeline and the number of scripts. For example, if the client's requirements need to be delivered in a very short period of time, then instead of four resources, I will take eight resources.

For any issues, we have to go to the Certify support team. They have a customer portal, and you just need to raise a request on the portal. Based on the priority, you get a response from them. Initially, they provide the solution through the ticket, but if the solution doesn't work, they also schedule a call. If the issue is not resolved in one call, they schedule more calls till they have resolved our issue.

I have used UFT in my previous company. Companies that have an SAP application or SAP Fiori prefer Worksoft Certify. For my current client, initially, we were using UFT, but because any non-automation resource can do automation in Worksoft Certify, we brought Worksoft Certify. Now, instead of UFT, we are developing everything in the Worksoft Certify. 

I am also familiar with Selenium. For SAP applications, Worksoft Certify is a very good tool. With UFT and Selenium, you need to create a framework, which is not required with Worksoft Certify. You can just go and develop an automation script. 

So far, I have used Worksoft Certify for the SAP application, the mainframe application, and the web application. For the SAP application, it is working well, but for the web application, instead of Worksoft Certify, it is better to go for Selenium. With the web application, we have the issue of values getting changed when developers make any change in the backend, and we also have a dependency on Worksoft for XF definitions. So, Selenium would be a better solution for web applications.

I don't have much idea about the pricing, but it is a licensed tool, and it is somewhat costly.

If you are considering this tool for your project or company, the Worksoft sales team would connect with you and explain what are the things that you need to perform. Initially, they give a demo, and after that, they discuss the licensing, etc.

It can be easily used by our non-automation resources with some training, but your team should ideally also have experienced people to be able to deliver within your deadline. For some of the development, you can also hire Worksoft resources on a contract basis. They would come to your location and help you with the development of a script in a short duration.

I would rate Worksoft Certify a six out of ten.

We mainly use Worksoft Certify for SAP automation, whereas we have web-based SAP and normal SAP background applications.

Worksoft Certify has helped organizations save time by using automation.

The most valuable features of Worksoft Certify are the way we can maintain the processes and sub-processes inside. We can immediately identify and replicate multiple objects in the application without having a major issue with it. We are able to do a lot of operations even with the solution being completely scriptless. That is a large advantage compared with other automation tools.

There are some other more complete tools than Worksoft Certify, such as Tricentis Tosca. It has a quicker way of taking in a customer's feedback with more efficiency. I do not see Worksoft Certify having a lot of progress over the years that we have used the tool in this area.

From 2014 to 2022, there were fewer improvements in the UI looks and feel. Overall there were fewer improvements in the solution. There were some challenges that we faced with our customers, and Worksoft Certify provides customer-specific call announcements. For example, customer A is trying to work on Worksoft Certify, they will face a specific challenge in utilizing the tool, and Worksoft Certify provides a custom solution to them. With customer B, they are faced with other challenges, and Worksoft Certify provided them with a customized solution. There is a chance that the same issue that was faced with customer A, customer B had also. Instead of Worksoft Certify providing a dedicated solution for everyone, they were providing solutions on a customized level. They can improve on this process.

There were some challenges that we faced with respect to automation. For example, there were some areas where we had to do a drag and drop of some of the objects from one place to another. In some of the areas in SAP where you have to perform a drag and drop, that feature was not available in Worksoft Certify. We had to find some alternate ways of doing those things.

I have been using Worksoft Certify for approximately three years.

The performance and stability of Worksoft Certify were good. We don't see a lot of issues or challenges that we're facing in this area. We have a 98 percent stability rate. We don't expect a lot of issues to happen in the application. On the SAP side, it was completely normal, it was working as expected, but coming to the web-based applications, when there are major changes. We have to remap the controls sometimes to ensure that the controls are working as expected.

Worksoft Certify is a highly scalable solution. However, it was a bit slower compared to the other automation tools. For example, Tricentis Tosca is providing major competition to Worksoft Certify and they are slightly a better tool. Whenever Worksoft Certify faces any challenges they're providing some patches to fix them, and that is helping the automation to grow faster and more efficiently. We have the layouts and plenty of recordsets that make Worksoft Certify more scalable.  

As an architect, I have to compare the support to other automation tools, there are some free tools, such as Selenium, where there is no support. However, there are some tools, such as Tricentis Tosca, where there is a dedicated technical support team who are available 24 hows a day seven days a week in the chat. We can directly chat and communicate with them. With Worksoft Certify we have to contact them directly and sometimes it can take some time, and the solutions that they provide are customer-specific. That is another challenge because when we have to work with multiple customers, this is another challenge that we face.

Neutral

I have been using multiple automation tools, such as Worksoft Certify, UFT, and Tricentis Tosca. Additionally, I have worked on other automation tools, such as Selenium and AccelQ. I provide solutions to the clients based on their requirements. I work on different automation tools.

We have a set of regression test cases that are already identified with the customer. They used to provide those sets of regression test cases to be used in their projects. We had to create some processes and sub-processes, such as our layouts and recordsets for the projects. Once we create all our sets, we create our regression suites using these areas and start working on them. We used to do a time-bound process where we needed to automate all these elements in a specific set of time that we had. Once we are done with the automation, we performed the activation of the sets in a cycle.

For the understanding of the requirements of Worksoft Certify, it did not take us a lot of time because we understand the process which is very important. Due to the specific functional area in SAP initial took the automation developers some time until they understood the functional requirement. However, once we understood how we were going to handle or manage the static and dynamic data, then the automation was simple using Worksoft Certify.

Once we complete the automation, our SMEs used to start utilizing this solution whenever there is any deployment. Instead of triggering the script manually, our SME triggers the automation scripts that they have the regression suite executed, and for other new automation scripts. Whatever the testing team tests the functional they started using Worksoft Certify for creating those automation scripts and started using them. There are different clients requirements based on the deployments. The deployments used to happen every two months, we have some regression suite to be executed, and whatever the new development that is going to happen, we used to utilize the dev environment to automate them and start executing them in the QA. This way they were faster and we can do instant automation.

We typically have a team of six people who were involved in the development of our particular automation scripts, and the exact number of people depends on the project that needs these scripts. For example, in my initial project where I worked on Worksoft Certify, we had a team of 13 people who were working for different process areas. We have different areas, such as production planning, retail management, and quality management service. Each area was handled by a specific developer and we used to have some teammates who were helping us and assisting in the automation of these scripts.

Normally it can take clients a lot of time for doing the regression. Using Worksoft Certify has reduced the time needed for this process. They don't need to replace all their SMEs for performing the regression because normally it used to take a lot of time for doing the initial regression activation. There were a lot of bugs that were reported and were reduced when we started using this tool. They used to use 10 people for doing the regression previously, for a span of a week. By using Worksoft Certify with using the automation scripts and 10 different systems activations happening, we saved a lot of time. We have seen a return on investment by using Worksoft Certify.

Worksoft Certify is slightly more expensive compared to other automation tools that are available on the market. However, the majority of the clients who are utilizing this solution, don't care much about the price. The main aspect the clients look for is its stability and reliability on the automation and whether they are able to rely on the automation scripts.

The solution can be purchased in different packages, some can include support.

I have evaluated lots of other solutions.

I have approximately eleven years of experience in this industry and over the past few years, I have been working as a senior architect.

Worksoft Certify is a good tool, but any tool can perform efficiently if you follow the best practices. If you're not following or utilizing the tool properly, there are chances that you might miss the opportunity. The main challenge with script less automation tools, such as Worksoft Certify or Tricentis Tosca is that you have to implement it along with best practices, and if proper best practices are implemented for these tools from the beginning, they can be extremely efficient and beneficial tools that can help to reduce efforts.

I rate Worksoft Certify a seven out of ten.

Its primary function is test automation. We record the test procedures and execute them in an automatic way. It gives us reports, in a centralized way, of all the information that we need to manage test automation for the ERP system and a few other systems as well.

We moved from manual regression testing, once a month, to continuous testing every second day, with the same scope or even an increased scope now. We don't need to focus on the manual regression tests, so we've freed up hands for support activities and new developments. I don't think that it has changed how our organization works directly, but we have become more efficient and more flexible.

In our estimation now, we save about 160 hours of manpower every month because we use Certify. It's 80 hours of robots executing the tests, and they're doing it roughly three times faster than humans. To do the same manually, and keep up with the general pace of development, we would spend 240 hours on testing every month.

In terms of codeless, end-to-end process automation across packaged applications, technically speaking there is some programming or development, like you would learn in middle school. But you don't need to be a professional in any programming language to run it. That's how we've done it. We don't deploy any additional software packages with it. We haven't developed anything else, other than using Certify steps to run end-to-end test automation.

Nevertheless you still have to have a mindset of a developer or an engineer. You need to have understand cycles and other primitive functional blocks. Still marketing-wise, I would call it codeless due to its simplicity. 

SAP is our core and the people involved with it are not always developers. Some of them are analytics or system experts. They don't know how to write C++ or Python or Java. But they can do testing automation in Certify themselves without help from a centre of competence (CoC). The only time CoC will participate is when truly complicated logic required such as runtime variables staking.

In usual situations, the skill set to start doing test automation needed is much lower.

There are a few aspects that are valuable. First of all, there is the screen-grabbing where you can pick up objects and it automatically recognizes them on the screen. Worksoft call it Certify Capture or LiveTouch. It's automatic capturing properties of the UI objects on the screen or on a mobile device for use in test automation scripts.

Other important feature is the modularization of the tests. That's an important feature not only of Certify but of IT tools overall where you create and reuse the components. Our test scripts are done with a "Russian doll" approach. That's standard for modern IT, however sometimes you see IT products without such functionality. Worksoft Certify's ability to build tests and reuse them is done pretty well and balances simplicity with flexibility.

Due to it, the learning curve improved even further allowing non professional test developers to plug-and-play test scripts. Such approach allows you to have that nice, modular end-to-end test. Can it get better? Probably not without sacrificing some other nice features and simplicity.

In terms of the core functionalities important to us there are the actual coding, great test data management, execution and reporting. Those are the basis, which are shared across many test automation tools. 

We also value that the test execution and reporting are stored in a database. We can extract the results and get the data out more easily comparing to text log files. That's different compared to other tools on the market. In Certify, we have a structured test execution and overall structured data.

Last not least is multi interface support is important for our applications landscape. With certify we can test SAP, Net, Java, Web and Android applications with one tool.

Certify's web UI testing abilities for testing of modern applications like SAP Fiori was good when we started and they developed it to be even better. We all know that web applications can change objects in DOM quite fast and it breaks tests. To counter it Certify has made object recognition more flexible and generic, so we don't have any troubles.

For standard and UI stable applications like SAP ECC 6.0 we have no trouble at all due to predefined objects and rich library of methods. That means we don't need to spend time writing a library, which could happen in some of the open source frameworks.

One caveat is that if you start running models in different parts of the end-to-end process — when you really try to hit the sky and make everything automatic, to cover multiple supply chain tiers processes in one e2e test, or similar processes that are really complicated — then tool simplicity turns into disadvantage. On other hand it stops us from unnecessary over engineering the test automation framework.

Architecturally, because Worksoft specifically built a database-oriented application, you essentially store code in the database. Git and text files orientation is more traditional approach with boundless set of tools to control versions, manipulation and analysis. But at the same time, Worksoft supplies us with their own version control inside Certify that has sufficient functionality for now. 

When it comes to mobile testing, we have a small bottleneck there. You have to buy third-party separate licenses if you want to test on a mobile. Business wise we see room for improvement there, although it's that really critical for us. 

None of these are showstoppers for our operations. Worksoft proved to delivery significant improvements in last 3 years and more we wait from 11.5 version. Overall, we are quite well covered with test automation related tools and nothing special is needed.

We've been using Worksoft Certify since 2017.

It's stable. Our approach is that we don't deploy the latest fresh version to production straight away. We wait for a few patches and follow with upgrade instructions. It doesn't matter if it's Certify, DB server, Linux or anything else.

Only case I could recall related to stability problem is a one mess-up in the database during over-few-versions upgrade about three years ago. It required some database cleanup with scripts provided by vendor support.

But looking at the overall stability, it doesn't go down or crash. SLA is 100 percent for us.

Because it is three times faster than manual testing, we can test more with fewer people. That gives us operational scalability already. Platform also has the Execution Manager tool if we would like to have technical scalability via a cluster of virtual machines. In addition Certify itself supports multi-agents, APIs, and integration with Jenkins and other applications including PowerShell. That means we can also develop scalable setup ourselves

As for overall scalability of Certify, licensing is the main bottleneck. You cannot scale more than you have licenses for. You cannot uplift your digital workforce just for one month and run 300 nodes strong cluster for a big upgrade tests. It is not different for majority of IT products, we don't see much of a problem for now.

Certify is our main tool for test automation for ERP, for PLM, and HR. It's covering two major applications that are at the core of any big machinery or manufacturing corporation. We continuously increase the scope, because systems are developed and extended.

We use their enterprise-level support and it pays out. We mostly use it for tricky situations. We often talk with 3^rd level, with architects and other experts behind the certify. It gives us good insights. Separate gratitude goes to active key account management on vendor side.

As for our improvement requests, we speak with the community and we speak with architects and provide necessary information. We don’t know do they take it into their backlog or is it just coincidence that Worksoft have provided most of things we asked for. In any case we get what we require for our testing, we in constant contant and we feel that we are listened to.

We did not have a previous technical solution.

The initial setup was pretty straight forward, in general. There is a database, there are clients to install, and you need a licenses server.

The key thing that you need to know is what you are doing, how you do test automation, in general. That's above the specifics of any tool. You must know how to slice system-under-test into functional components, make the right model for reuse. It is important to break down end-to-end testing into smaller reusable items. That's not trivial, and you faced such challenge with any tool. You have to know what you're doing.

The deployment included one of week training and then a proof of concept for a couple of months. We ran typical end-to-end process in the proof of concept and found our ways to deal with above mentioned slicing, development guidelines and how to establish roles. There are useful guidelines provided by vendor as well. Overall it took about one quarter from the GO decision to start running regression tests.

Our approach to testing is as a "safety net," so we don't need to have end-users who run it and hunt for new defects. It's just continuously testing given scope and raises a red flag if something goes wrong. Such approach secures an immediate feedback for the development team or for the quality assurance team.

End users are not involved into testing usually although we could run hybrid testing with a mix of automatic and exploratory tests.

We didn't work with any third-party. There was initial training from the Worksoft itself for one week. That was it.

The return on investment, when we count the 160 man-hours we save monthly, will take about seven years for our scale

License model is a traditional one. As with any other manufacturing company, the software testing is not our core business, it's not in our interest to invest capital into the licenses. It would be preferable to have a pay-per-use model. At the same time, it's a fair game, for now. 

Aside from their standard licensing fee, if you want to have enterprise support, there's an additional cost.

We have done a few comparisons and we're continuously looking at the market to see if there is anything better, cheaper and more suitable. Market is changing a lot, RPA solutions expanding to test automation market, Robot Framework ecosystem is thriving and some other established vendors are operating. We're keeping an eye on it for evaluation. So far, cost-wise, feature-wise, and in terms of the learning curve or skills requirements, we are good with Certify. From our comparisons now, we would pick Certify again.

As always, you have to know what you're trying to achieve. You also have to think about how do you model your system-under-test; how it is written, the quality requirements and standards. The key benefit comes from reusable test scripts. 

When it comes to Certify itself as a tool, keep your eye on objects. If you map something, keep a good inventory so you understand it and you don't put all the objects in one big basket.

For me, the biggest lesson from using Certify is that you can do quite interesting and complicated things with the codeless approach. You don't really need a complicated programming language to do testing. 

Overall, I would rate Worksoft Certify an 8 out of 10. Of course we would like it to be cheaper and more powerful and developed faster. But are there products that I would rate a 9 or 10? I don’t thinks so. It's at the top of the market from what we know about the market.

The reporting feature is something we look forward to. Also, the Worksoft training that we have done was mainly on the web application along with SAP, SNOW, and Silverlight integrations with the tool. It works efficiently with any tool. The projects we mainly used were for the testing of SAP applications over the web. 

Automating the User Acceptance Testing (UAT) process is the most valuable feature of this tool which helps us save loads of time for our clients on the projects and also generating testing and other reports.

We are doing Worksoft Online Training and also take up various Worksoft automation testing projects. I have totally trained about 50 participants on this tool. Most of the trainees are happy to learn and use this product in their jobs now. We have also done two projects, one for retail sales chain and another for a banking project. Both of the projects were delivered on time and the clients are happy to generate some automated OOB reports and also create their own Receipts. The clients were happy with our timelines and also with the training we offered at the end of the implementation.

Most of the features are good. However, being codeless is the best feature that makes it easy to use for those who have done any coding but understand simple English like commands. Anyone with basic knowledge of using a basic tool can learn and implement the solutions with Worksoft. This is why we have been able to train so many consultants on this tool and they use the same in their jobs currently and keep referring us for more candidates. We recommend using this tool for your automation testing projects.

Pricing is a bit high and we would like to have the availability of a trail environment for beginners and training would be great to have and easier to expand and use by more and more consultants.

The bigger reports needs to be more customized by the tool for better use, also tool also can be further simplified by a better Graphical user interface (GUI) will help us a great deal while taking up projects. 

We look forward for these upgrades so we can enjoy using the tool more and help others learn this tool.

I have been using this for the past three years. It has evolved as a codeless automation tool for testing. We used sed 10.0.1 and are currently using 11. 

We have also used few other tools for our trainings. 

ROI is pretty good so far.

We would like to have a cheaper version for a single user/trail version of the same for our trainings. The cloud based environment should be available free for the trainings for 15 days or so.

We do trainings on a needed basis so we understand the demand of various tools in the market. We strongly believe while Worksoft is a good tool it is losing its potential a bit to other tools in the market. The demand for training has gone down in the last two years.