At a time when face-to-face communication has to be avoided, working remotely is a top priority. A Finn on an average day performs tasks that can run an estimated 10 million lines of code. When it comes to large companies with massive software packages, we are talking about unimaginable amounts of code.
A case in point is the SAP environment. How can its quality be ensured through test automation, regardless of time, place, or situation? When it comes to SAP CRM testing and even more complex integrated systems, where do you start, and what needs to be done?
Regardless of the different SAP testing services you use, the first step is to gather relevant background information. What kind of SAP environment is the automation being built for? What is the user interface going to be like? The most important step is to decide whether to use SaaS (software as a service) in the implementation of Qentinel Pace or a Hybrid solution.
This choice is often determined by the customer's information security policy. In the SaaS option, all Pace components run in the cloud, which is connected to the tested SAP environment. However, if the customer's information security policy does not allow for a purely cloud-based solution, different options must be weighed. For example, if the machine on which the robots work must be in the customer's own data center, then it is more feasible to choose a hybrid solution.
If Qentinel Pace is deployed as a SaaS service, the benefit is fast deployment. Test automation is activated immediately, with no time required for separate installation procedures. In addition, the customer does not have to purchase any hardware to implement test automation. Qentinel maintains all the technology needed to test the SAP environment on the cloud. It takes an estimated 5-14 days to deploy Pace as a SaaS service.
With the hybrid approach, special attention is paid to data security. Customers often zero in on the hybrid solution when they want test robots to run on their own intranet. In such cases, test ‘robots on-premises’ — a local device or a virtual machine on which Pace components are installed — establish an encrypted connection with Qentinel Pace. While test robots can run from this local system, the software can still be managed online. A service connection is also created so that components of the local test robots can be updated remotely if needed. The implementation of the hybrid solution can take anything from 5-20 days as it may take time to set up the test robots on-premises.
In both the implementation methods, permissions for the SAP environment are defined and created so that the robot has the right to perform the test when connections are in order. When the functionality of the connections is tested, the customer gets to experience a few test case runs even before the actual testing begins,
So, that brings us to the question. What automation use cases should you choose and on what grounds? It is important to select the most critical business processes for testing which can secure complex end-to-end processes. Once the processes are documented, it is possible to foresee potential problems or anomalies and plan what Qentinel can do in such situations.
For test automation to succeed, human commitment can be crucial. Everyone involved in the process from the Qentinel experts to the customer's IT service provider needs to work together. This way, the test automation process can progress smoothly and rapidly without communication gaps or waiting times.
The quality of the code that runs the software can impact the functioning of a whole organization. At Qentinel, we believe that the quality of software marks the quality of life!
Contact us and we will be happy to tell you more!