Worksoft was fabulous help with the setup. They would get on a call anytime. They would help us walk through issues and help us figure them out; even how to navigate our systems. Their assistance during the setup was phenomenal.

The deployment typically takes one to two weeks. The first step involves setting up the database, determining the server specifications, and installing the servers based on the specific requirements and data activities of the project.

We purchased the software, then we found a vendor on our own to help us with the development.

We used Worksoft team initially. That helped us through the setup and other things. They did a great job. We probably automated about 275 tests in less than five weeks, including the setup. 

I suggest people go head and use Worksoft, along with their services, when you buy the tool. They will help you to onboard it quickly and set it up for you. They will do lot of the automations. They will help you with lot of these practices, then you can take it over from there.

We did the deployment ourselves. It took less than a week. Internally, we had one system administrator do the bulk of the work.

We ran the deployment on Windows Server. We have two machines: a database server and an application server. Our test developers can logon via Windows Remote Desktop to access those machines. They built all their tests out on that system. Architecture-wise, it is hosted all behind our firewall, but it is all server-based. No one is building tests on their local desktops. It's all server-based, and we can share some of our scripts amongst our team members.

My primary team is offshore. They are in India and Bangalore. Therefore, all of the test development is done there. However, we can access the central test library seamlessly, and  the test strategy for setting up and standing up servers and installing the software was pretty straightforward.

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

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.

We have Worksoft help us each time that we do an upgrade or implementation. Our  upgrades have gone smoothly.

We have always worked directly with Worksoft, along with support from our internal resources. Worksoft has been delivering excellent services through their managed services model.

There is a separate team in my company who has taken care of the product's deployment phase.

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

We implemented and developed in-house expertise. A vendor team would have accelerated and made adoption smoother.

In the beginning, we had an integrator, Cognizant, who created a lot of scripts, but we stopped because we had a contract with them that they would install Worksoft, but it was not allowed. In the end, they just did some automated scripts for us. Our automation team in Bratislava was not satisfied with the quality in the end. We want to have a flexible style with quality, and this wasn't done by our Cognizant colleagues. Therefore, we decided to do it on our own.

From Cognizant, they were sold as SAP and Worksoft experts. Concerning Worksoft, I cannot say if they're expert or not. Concerning SAP, not all of them were experts, maybe one. However, this is always the same in this business. We also had cooperation with Worksoft. Concerning the flexibility of the scripts, we decided to work on our own.

We expect partners too be really good. Otherwise, the company does not see why we should pay for them.

There are separate server and database teams who have their own SLAs for deployment. It all depends on different project specifications. 

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.

The company used a Worksoft consultant for the deployment but I don't know her name.

We, as a company, have good contact with one of the Dutch Worksoft managers and he introduced the integrator to us, as that manager is from the United States. The consultant came over for a week to give us some training on a number of things because we are not only using Certify.

They were really happy with her. A lot of questions were answered, a lot of issues were resolved. She was able to contact Worksoft support really fast. They had a blast while she was here.

The IT department and I worked with a Worksoft deployment engineer because of all of our Worksoft infrastructure. She walked us through setting up the database in SQL and the MongoDB with Worksoft Analyze. It was a pleasant experience. Most of the issues that we ran into were because I did not know something.

We mostly deployed it ourselves. We had some consulting services from Worksoft. They helped in the initial set up, especially with setting up the Best Practices.

Worksoft did the deployment. They were awesome. 

We worked with Charlene Smith. She did the installation for us.

We used the Worksoft for the deployment. They came and helped us. We have a good relationship with them.

We define certain different criteria. We check if the vendor is giving support for the tool, and we also evaluate the price. Of course, we also take note of the ROI of the solution.

We used Worksoft for the deployment, who was very good.

When you are implementing Worksoft Certify, it is probably best to bring some Worksoft consultants in to help get you setup, and set it properly. Because if you don't get your initial systems, like your folder structures and your naming conventions, set at the beginning, there is a lot of rework to get it to work. We did have to go through that.

It was just one or two people from Worksoft and three guys on our side.

As far as training, they have a very comprehensive training program. I'm sure it's all ... I'm sure it's very good. What we did and what helped us to be very successful is we went through and did live test cases as part of our training.

Instead of spending all the time going through the books and learning the tool in and out, we went through and we got right into creating our test automation with the trainer that they sent out. That hands on experience was, it was priceless. It helped us to be successful and get going with creating all of our test automation.

The implementation depends on the client's business. Overall, it is not very complex. It is simple and easy to implement. There is no need for a third party integrator.

We deployed Worksoft Certify in-house. The deployment did not take much time at all. It took just a few hours. 

Because I have been using Certify for so long, I do my own implementation, except for local DBA support for the database. However, for brand new implementations, Worksoft has an excellent professional team for just that purpose.

We are still deploying. We started with what we called a 'pilot'. We gave them around 300 manual test cases, which we got down to 141 test cases as part of our pilot. We ended up reskinning out website, and consequently, we had to go back and touch all 141 test cases. Some of them have now become irrelevant with the reskinning of our site. Therefore, we had to go back and reanalyze all of them, and find the ones which were still relevant, which were 90 to 95 percent of them. Then, we had to touch them up. We are in the process of doing that now, touching up our old test cases and building new ones on top of them. This took us a good six months, but we are starting to run regression tests now, though they are not formally in place.

We hired resources from Worksoft, but we do have our own testing groups. We have also hired some Worksoft certified people. We have been using Wipro for Certify testing and development, but our experience with them is not so good. 

Wipro was our testing vendor for manual test cases before we brought on Certify. My guess is that they did not want to lose our business because they told us that they knew how to work with autotest cases, and they didn't. They told us they knew Worksoft Certify, and they didn't. They were given a second chance and hired some Worksoft certified people, but it was a really big headache.

For deployment, we have two people from Worksoft and five or six Wipro people. The Worksoft people are far more productive, since they know the tool better than anyone, but they are more expensive as well. The Worksoft people are sharp. They notice things in our testing and point things out. Their understanding of test cases is off the charts. They picked up our systems very quickly. Wipro has been a bit more of a drag. It is because they're learning Worksoft Certify and don't really know the tool. We also have one or two business people involved who are not developing test cases, but they're project managing.

We are still building test cases, but we are running the testbed that we have, which is a few hundred test cases. However, we only need one person from Worksoft to maintain this.

Make sure you involve Worksoft while you do the installation. Follow their recommendations, which are very important, from framing of fuller structure designs or choosing the right capacity for the server. Their box of recommendations are definitely required.

Worksoft did the implementation. Our experience with them was great.

Later on, Cognizant took over from Worksoft.

We worked with a consultant for implementation.

Our internal IT team performed the installation and there is no maintenance required.

We used a vendor, I would rate them 7/10.

In-house installation was done.