What is your primary use case for Worksoft Certify?

I primarily used the platform for SAP projects.

We use the solution in pharmacy and retail.

In my company, the solution is used for SAP automation.

It serves as our primary automation tool, specifically utilized for testing purposes. The tool predominantly finds application in functional testing and integration testing for our customers.

Worksoft Certify is an automation tool used for functional testing.

We are in the retail business, so our primary use case is automated regression testing on our supply chain. It helps us oversee our internal economy, including the warehouse, HR, and the stores.

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.

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.

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.

Our primary use case for Worksoft Certify is the automation of test cases. Performance-wise Worksoft Certify is very good.

We use this solution mainly for SAP automation and for some web applications and we also use the reporting feature. I'm a quality assurance project manager.

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.

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

We used the Worksoft director access to test automation.

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

Our use cases are mainly from different domains for mobility solutions. It is also for HR and eCommerce.

We have an SAP environment, so we use Worksoft for SAP and the ecosystem around SAP. Most of the use cases are related to SAP products or interfaces and the applications that are interacting with SAP. We use it for test automation. We are basically using it for regression testing, especially for our releases. For example, in the big SAP systems, when we have support package upgrades or bigger function releases, we use end-to-end test automation to ensure that the changes are not impacting the processes in the system. With this test effort, we can make sure that the releases are running without any issues in the production systems. We started using it around six years ago with an on-prem installation, and we had a pretty good experience with that. The way we are using the software is that we have installed it on our terminal server so that not every tester has to install it on his own machine. Having this terminal server environment is allowing us to really stick to specific standards in terms of how the software will be used and in which sequence updates will be distributed on the server. It also helps in terms of the connectivity to the systems that we require for test automation. It makes it quite easy for people to concentrate on developing tests and not on the environment. We are running version 12.0, and 2006.77 is the patch level.

The primary use is developing automation on SAP at a medical device company moving from Micro Focus UFT scripts.

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.

Our primary use case is for SAP regression testing. We wanted to have our all SAP processes for regression to be optimized using Worksoft Certify. It took around one year for us to take that process and learn how it works, gradually improving it until now. We do regression testing on a weekly basis using Worksoft Certify. This does not include just SAP. We are also using the web-based tools when we are integrating end-to-end processes. When we are moving within one end-to-end process, we are shuffling between all the scripts and then going back to SAP. It works quite well. At some point, we will have an RPA initiative to use this solution. For example, we need to obtain data from our development environment to check reports and verify them, then create transactions using Worksoft Certify. We have more than 160 end-to-end processes. In our repository, we can have one transaction process or more than 40. There are big end-to-end processes and there are smaller ones. There are processes that can take hours to run and there are processes that can take a couple of minutes to run, but most of the end-to-end processes have multiple transactions. In weekly/monthly releases, we don't have any type of manual testing. We are just relying on Worksoft Certify for its test automation. We also use Worksoft Certify for test automation in projects. For scheduling, we are using an Execution Manager from Worksoft Certify.

Initially we were automating the regression suite for SAP ECC. From there we moved into a web application called HVAC Partners, which is something that we've developed that is a type of customer portal. That application also connects to SAP, but it does some other things that don’t necessarily connect to SAP. It is a kind of front end for quotes and sales orders that go into SAP, but it's also reporting status of orders and status of warranty claims and the like for the customers. From there we moved into the Middle East SAP ECC instance and automated their regression suite and, from there we rolled out S/4HANA for our service business. With S/4, SAP releases updates every quarter. Because the S/4HANA instance is in the public cloud we have two weeks, essentially, to regression test and test any new functionality. We started with the last release and we did about 70 percent of the testing with Worksoft. We also used the S/4 automation tool, which is more for unit testing so it's not as valuable as Worksoft. We're wrapping up that automation in about the next month and we'll be moving on to a European rollout of S/4. We'll just start working our way across Europe and those implementations. We have it on a virtual server and we're using remote desktop access for the offshore automation engineers to access it.

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 use it to do end-to-end testing for the business. After development has occurred and once we're into verifying that no regression has been broken, it's at that stage of testing that we deploy it.

We get user stories from the DevOps teams, in conjunction with a recording they make with another Worksoft tool. Then we will investigate if it has already been automated and, if not, to automate the process which has been delivered to us. This is all set up in a Citrix environment. We have SAP being used at the moment and we still have the old SAP ECC up and running. I'm not sure which part of this is cloud-based, but the Certify solution is installed on Citrix.

The company is using it across our IT landscape on different projects. We use it to test web applications, SAP mainly. Right now, we're doing a big conversion project. The one that I am working on is a big conversion from an old mainframe system over to SAP. Thus, we are using it to automate all the UAT test cases. We have also used it in other areas of the company for ServiceNow upgrades and general web design stuff.

We used Worksoft Certify with SAP ECC and Fiori applications in the beginning. We extended that to the ServiceNow application. We have up to 15 modules in ServiceNow with 750 test cases. Our regression testing suite is around a 1000 processes.

We use Worksoft Certify for testing and non-testing. * Under the testing umbrella, we use it for regression testing, disaster recovery, validations, and system refresh testing. This has been our main focus. * Recently, we have started getting more requests for more RPA-light type of work, which is not testing. It is using the same skills, process knowledge, and tool sets to do work that would replace manual repetitive tasks with automation. We use Worksoft Certify for some basic ServiceNow functionality or Workday releases, weekly and quarterly releases. For SAP Hybris and ECC, we are also using it for our internal security protocol testing. So, we test Office 365 and Windows 10 compatibility. We test some Excel functionality and file sharing, as part of our security protocols. The most in-depth end-to-end testing that we have is in SAP. We have done a lot of manual testing. We still do a lot of manual testing for our projects. We've eliminated a significant amount of manual testing with our system refresh, automation, and for technical upgrades where changes are known. However, for projects with new enhancements and functionality, we are having a slower time penetrating into them. With regression testing, we have completely replaced it with automation. Now, we are trying to shift as much as we can to start automating processes earlier in the project lifecycle, but it has still been a bit of a challenge. This is one of our stretch goals for this next year. The non-testing area is where we have had the most growth over the last six months.

My company brought on Worksoft to assist us with an SAP upgrade in order to make it so the testing was less stressful for business users through automated testing.

The primary use case is for SAP applications. We do some end-to-end testing of applications. We created a checking and boarding process for a flying scenario, which was innovative. For the back-end systems, we use it to do financial valuations. We also have a SAP HCM module and SAP FI module where we are actively using Worksoft for our current automation.

The primary use case is regression testing and test automation. We use this solution for end-to-end testing of packaged applications, like SAP, ServiceNow, and some in-house web apps (which we built).

Our organization is building a platform which supports a client across SAP end-to-end. As part of it, we have reconfigured go-to market solutions across industries and functions. Now, specifically for SAP, we use Worksoft to test these reconfigured solutions, as these are very critical. As there are newer versions of SAP and we are building our solutions, we need to ensure our solutions can do regression testing. The second important aspect is these are real visible assest which we take to the client. So, not only having preconfigured systems, but being able to test it where clients have Worksoft, it gives us an edge.

The primary use case would be for automating SAP. We did attempt to automate some non-SAP processes, but had mixed results. We do have some areas which are already using it for RPA-like use cases. We use this solution mostly for end-to-end testing of SAP.

We have been working on test automation for SAP-based platform for the last 15 years and leveraging Worksoft for SAP test automation in last 10 years. We have some fantastic use cases on how we can leverage Worksoft in large SAP transformation programs, especially for major global rollouts. If you look at some of the industries, like retail and logistics, we can see a lot of consolidation. When there is consolidation, we need to merge two SAP landscapes to a single landscape instance. It is a very complex transformation program. The testing is labor-intensive work in such a large scale IT landscape program. Worksoft has played a key role in delivering these complex integration programs on time, because we automated the core processes using Worksoft Certify. This helped us to automate the testing scenarios in new companies being integrated. At the same time, we test the existing company codes on the existing landscape to ensure that business as usual is not impacted. If you look at the industry trend, the next six or seven years will be SAP S/4HANA migrations and adoptions of SAP cloud applications, whether it is SAP SuccessFactors, Ariba, or Fieldglass. We strongly believe that WorkSoft can play a pivotal role in delivering large-scale SAP S4 HANA programs since Worksoft can support the implementation of SAP cloud applications. We have delivered a couple of major SAP S/4HANA programs by leveraging Worksoft Certify. One of the key things that we have done is introduce test automation on day one in system integration testing (SIT). We don't want to wait until the program is over, then start the automation development. We start the automation right from the build phase, then we are able to deliver test automation on day one to the SIT.

We primarily use it for ERP testing. SAP is the primary application for the client, which we test using Worksoft. We use Worksoft Certify for end-to-end testing of packaged applications. We have applications, like SAP, connecting with third-party applications, such as Oracle Transportation Management and other web applications. We have these type of use cases implemented and they are working pretty well. We also use this solutions for web UI testing of modern applications.

The primary use case is SAP applications and customized web-based applications. Now, the company is moving into Salesforce, which is something big for us. I've worked on multiple projects and our customers are very happy using it. The company is also very happy with the tool.

It is not for the entire automation process. It is mainly for anything which needs to be automated. Instead of just replacing human work, which it is doing now. It also includes robotic process automation for when we are replacing centralize manual work. Our clients use Worksoft Certify for end-to-end testing of packaged applications and web UI testing of modern applications. I have been using BPP and Execution Manager for more than seven years. I sell the product to different clients.

We automated a big end-to-end process: Hybrid to SAP to Manhattan, then back to SAP. We have web UI automation testing. Hybrid is a type of web UI testing. We have SaaS automation testing, along with CRM testing. We also have Manhattan, which is a third-party application.

We bought the product in 2014, but did not have the right structure in place to use it properly. It wasn't until 2017 that we started to receive good value out of the product. Automation is now part of our strategy. We use this solution for end-to-end testing of our packaged and SaaS applications. It is very much a part of our key strategy. We have it running end-to-end updates all the time. We do web UI testing of SAP and ServiceNow. This was difficult in the beginning, as we had a homegrown product, and we had to do the proper object naming. With SAP, Worksoft does the object naming for us. This improved our website from 2014 until now. This is part of their process improvement.

We have automated quite a number of test cases in last year.

We have been using Worksoft Certify for ten years.

Primary use case is for SAP support testing.

Our primary use case is test automation. We have an SRP solution called One1ERP on an ERP platform. We started the automation in Worksoft Certify, getting more than a thousand test cases automated. Nowadays, we also have automation for a web application in our HR area, so all our HR processes on the platform, Pega. This started to be automated since November last year. We have 40 test cases automated on this application in one year.

The primary use case is to automate their SAP and Web applications. We use Worksoft Certify for end-to-end regression and integration testing across our systems.

We're using it to move manual tests over to automated tests to use on major programs and projects going on within the company. We are also moving to Dell EMC Embedded Boxes for an agile approach from a waterfall approach, and part of our new addition for 2019 after merging with a new company. Our role now is to automate as much as we can for usability. We're doing mostly end-to-end testing scenarios. We use it on SAP and ServiceNow web services, along with SRM, CRM, and various applications.

Our eCommerce platform is Hybris. We run end-to-end tests where we place orders in Hybris, then we validate the order in ECC. Additionally, when an order is placed on Hybris, our QA environment has a lot of things which the SAP analysts have to prepare to get an order ready, so it doesn't clutter up the system, such as creating deliveries. Worksoft can do this for us as well. Hybris is out most modern application. Our point of sale system is web-based, and it is in web form. We are on Azure. One of the things that we've been able to do is use Jenkins to put our Azure machines on business hours. We tell them to turn it off at 5 PM, then we tell them to turn it on at 7 AM. This has saved us about 62 percent of computer operations.

The primary use case is more on SAP for automating all our manual business work, as well as doing regression testing. We do end-to-end regression testing on SAP. The product has worked very well with SAP.

We are using the on-premise version and testing an eCommerce platform: SAP Hybris. This would take in all of our vaccine orders over the Internet. That is primarily what we are testing it on.

We use Worksoft Certify to test our SAP System. We have a global instance of SAP, which we started implementing in 2012, and we are still in the process of implementing. We have rolled out SAP to about 80 percent of our manufacturing and distribution. Right now, the remaining projects are a small distribution center and sales offices. We have ongoing projects, and three times a year, we release a new version of SAP. We rolled out SAP to a new geography, and we also added new features for our business users. Thus, as part of those projects, we use Certify to do regression testing of our existing business processes, and we also use it in the project to test new functionality. When we are rolling out in a new country, we do a configuration for that new country. We use the automation test to test the business processes and prices of that new country. It is sort of semi-automated. Our business analysts generate sales orders from the new country, and we will run them through the shipping orders to cash, the shipping steps, and the concrete steps. Then, we get a set of documents to review. The business analysts review those documents to make sure the order is processed correctly. So, it's not fully automated, but it does help cut down on testing a lot when we roll out to new countries. For regression testing, that is fully automated. We have tests where the software checks the results and either returns a pass or fail. These are run as a regression suite anytime we push a change to production. We do use it for the end-to-end testing of packaged applications, primarily SAP. We do have some plugin applications that we use it to test, which are part of the business process. We use Salesforce for CRM, and we have a custom built eBusiness application. While we don't do extensive testing of those applications using Certify, when the business processes touch one of those applications, we do cover those application with another certified test.

Initially it was to automate our SAP ECC regression suite, but we have moved into web applications at this point. Our SAP has interfaces with web applications, such as a quoting system, and dealer and vendor portals. Some are applications that we use internally and some our customers and dealers access for a variety of reasons, such as placing an order, checking status of an order, or filing a warranty claim. We have now moved on to starting the automation in these systems because our SAP Suite is probably now 90 percent automated. When you're dealing with an external system, e.g., warehouse management, it is owned by the outsourced vendor. We don't have access to their test systems, so we can only automate up until we do our hand off to them. We automate our test up to the point we interface with their system. They complete the test in their system, then send us back a file. We pick up the test from there. It is a little manual, but that is what you have to do with systems in which you can’t access. We have a couple web applications and a dealer portal. There are certain functions that we can't automate for a variety of reasons, it doesn't make sense, or they are so simple that it's just as quick to do them manually. We started using the product in late July 2016. We are using version 10, but will start beta testing a version of 11 soon.

Worksoft Certify is being used to run automated weekly regression tests across some of our primary SAP systems in line with our Change and Release management strategy. These tests run every weekend without fail. The results are reviewed on every Monday morning to check for failures and to analyse if any failures are associated with the changes scheduled to be transported to the production environment that week. Failures (if any) are fixed and the tests re-run before transporting the associated changes into the Production environment. We also utilize it for projects that need extensive business-user testing and functional testing. There can be testing requirements which come at short notice which can take three to four weeks of manual testing effort. By using Certify, we have been able to bring timescales down to a few hours of automated testing effort. Our final goal is to utilise this for 'Unify', our new global solution which is currently being deployed, which will deliver common processes and systems to all sites and sectors, replacing all our existing legacy systems which will demand extensive regression testing.

We are using Worksoft Certify to enable our stakeholders to do test automation on the UI level. We use it for end-to-end testing of packaged applications. We are part of the internal IT department within our company. Most of the time we are using it on our own products. The products and systems that we get are usually preconfigured and prepackaged and we do additional testing, not just for the functionality for the coding that we add to the product, but also on the prepackaged solutions. We use it for all kinds of applications. Our focus is the web area, including web-UI testing of modern applications. We have two tools in place: our own internal corporate test automation tool, and Worksoft Certify. The latter is a complementary tool, especially in the web area where there are some white spots for our corporate tool which it cannot cover. That was the main reason why we brought in another tool. And for that, it fits perfectly.

We have developed some end-to-end regression testing scenarios that we've found pretty valuable, so we have created a bunch of processes in Certify, linked them together, and we use them every week - sometimes more than once a week - in regression testing.

We use it for SAP and ERP. I think from the SAP and ERP point of view, it is very good.

SAP HANA S/4 HCM, FI, BI, Payroll, SuccessFactors, Fiori, other web HTML interface applications.