Ways to formulate a Quality Engineering strategy

 

Today, enterprises are facing a multitude of challenges such as a rapidly changing technology landscape, a plethora of customer touchpoints in an omnichannel environment, rising customer expectations, and budget constraints, among others. To meet these challenges as well as to create value and deliver quality software, enterprises need to follow a robust software quality assurance strategy. However, these would entail using scalable and reusable assets to test and integrate the software modules in the SDLC.

Shift-left testing in the Agile model of development allows for testing alongside development and has the ability to detect glitches before the code goes into production. In a day and age where enterprises are required to deliver top-notch quality products in quick succession and provide periodic updates to let them function in an omnichannel environment, quality engineering is the way ahead.

By taking a quality engineering approach, enterprises can ensure the software product aligns with the business objectives and meets the quality standards. It ensures the product is designed in such a way that glitches or vulnerabilities are eliminated, and the final product emerges sans any performance issues.

Quality engineering has assumed increased salience due to the rising incidences of cybercrime. It is common knowledge that cybercrime is able to spread its tentacles due to the prevalence of glitch-prone software applications, not to speak of a user base indifferent to the requirement of stringently following the security guidelines. QE services can integrate various checks and balances in the software hierarchically to minimize the impact of cybercrime. Any software quality engineering services would involve the following (and more).

• Uphold the quality of the product or service as per the project specifications, quality standards, and business requirements
• Plan the quality assurance strategy
• Data collection and analysis
• Detection of defects
• Identification of risks in the value chain
• Analysis of the end-user feedback to enhance the quality of the product

Reasons to implement quality engineering

To further add to the points mentioned above, enterprise quality engineering needs to be implemented in the SDLC for the following reasons:

• To achieve the highest quality for the software product
• To ensure that all business requirements are met
• To minimize the chances of software failure due to the presence of glitches, bugs, or vulnerabilities
• To avoid expenses on implementing changes on the product after its release
• To deliver superior customer experiences and increase customer satisfaction

Core service offerings of digital quality engineering

Quality engineering is comprehensive in its scope and touches every aspect of software development. The core offerings may include

Agile/DevOps testing: Testing of the code is conducted simultaneously with development and includes the operations as well.

Service virtualization: Since various test variables are not always available in real-time, their absence may impact the quality of testing negatively. Thus, using service virtualization, the required assets can be generated virtually and used in the testing process to deliver better outcomes.

Security testing: An essential part of DevOps, security testing is about identifying the vulnerabilities in the product/system and fixing them to prevent the ingress of malware.

Test automation: Manual testing can be exhaustive for testers and may allow the inherent glitches in the software application to escape their attention. However, by automating the testing process, certain repetitive tests like regression testing can be conducted non-stop leading to better identification of glitches.

How to formulate a result-oriented strategy for quality engineering

To empower the digital transformation journey, enterprises need to re-engineer their QA and testing processes and implement software quality engineering in the following ways:

Integrate quality at the top: Any quality engineering company would entail buy-in from its management to implement changes in its workflows, tools, teams, and methodologies. At the same time, the management can let the workforce know about the benefits of implementing quality engineering and adopting the new system.

Make test automation an integral part: QE services have to run continuous testing on the software application to validate its quality against various metrics. Continuous testing shall involve people, processes, technologies, and tools. Here, test automation can be a handful while checking repetitive processes like regressions when a new change is introduced to the code. Further, writing the right test script to execute automated testing would require the selection and usage of the right tools.

Collaborate with teams: As digital quality engineering may need developers to function as testers and vice-versa, there should be a synergy among cross-functional teams. QE is also about driving accountability across processes to ensure quality by using the right technologies and tools.

Use of AI and ML: The implementation of the QE process may include the integration of AI and ML technologies for better analysis of real-time data, metrics, reports, and logs leading to the prediction of glitches.

Conclusion

Quality engineering has become a critical part of the software development process given its myriad benefits and the capability to eliminate glitches beforehand. It ought to be adopted by enterprises to develop and deliver quality products.

Article Source:

https://huddle.eurostarsoftwaretesting.com/

How are Agile, DevOps, and Continuous Testing connected

 

Digital transformation brought about by quality software applications and robust hardware platforms helps to create a competitive advantage for enterprises across verticals and geographies. Now it is no longer about choosing between speed or quality of software but to incorporate both when delivering to the end customers. With Agile and DevOps being embraced by enterprises to stay up the competitive curve, Continuous Integration (CI), Continuous Delivery (CD,) and Continuous Testing (CT) have become the catalysts to drive quality digital transformation.

It goes without saying that Continuous Testing has become critical and challenging. Further, CI and CD are primarily tool and team-driven activities while CT is comprehensive in its scope. It includes teams, tools, testers, and services. The importance of driving and integrating code changes cannot be ignored in the SDLC. At the same time, unless the automated delivery system can figure out the impact of such code changes on customer experience, CI and CD could become meaningless.

The rising competition and changing market dynamics have put pressure on enterprises to innovate and change. And Agile and DevOps in consonance with continuous testing offer the framework to address the requirement. At the heart of digital transformation lies the need to deliver software quickly, safely, and reliably, which can be achieved through continuous testing in DevOps.

Why continuous testing?

The customers of today are wont to use software applications across a plethora of devices, operating platforms, browsers, and networks. They want the applications to be high performing, navigable, scalable, secure, intuitive, and fast-loading. These attributes can only be fostered if the software development process supports a robust QA mechanism in the Agile or DevOps mold. Unlike in the traditional or manual way of testing where QA comes after development as a separate discipline, the Agile or DevOps model has QA being part of an integrated team with development.

In Agile testing, the software under various stages of development is tested for performance, security, usability, scalability, and many more. Thus, glitches are identified and fixed early in the SDLC leading to the delivery of quality software. A continuous testing strategy enables enterprises to put in place the processes, systems, and automation to accelerate the time to market, install improved feedback loops, and deliver desirable business outcomes. The outcomes, on their part, comprise top quality products and services, operational efficiency, responsiveness, competitive differentiation, and enhanced customer experience.

The continuous testing services create a quick and risk-free feedback loop for the QA specialists in the Agile testing pipeline to understand (and act upon) the issues faced by the end customers. These services help to manage business risks borne out of the complexity and pace of application delivery.

Why Agile-DevOps?

To thrive in a competitive business environment, enterprises must address issues like time constraints and resource mobilization to build-test-deliver applications that are qualitatively superior, secure, and stable. This engenders a renewed focus on continuous test automation and collaboration.

• The DevOps approach is ideal for enterprises that struggle to manage demand and implement rapid changes in the SDLC.
• DevOps allows enterprises to address their acceleration and integration needs by establishing a toolchain that cuts across the realms of development, QA, integration, management, and delivery.  

• The silo-driven Development and Operations teams should be integrated to drive better collaboration. Further, the pipeline should have a built-in mechanism to receive continuous feedback and to generate better quality features and functionalities.

DevOps: the extension of Agile

In the Agile model of software development, developers create user stories comprising smaller chunks of the build to generate feedback loops and to align the product to the market need. It started with small teams comprising developers and QA testers working collaboratively and efficiently. Thereafter came the notion of scale wherein the software code was developed in short iterations. However, down the pipeline, when it came to deployment and receiving feedback, the silo-driven processes stifled what was expected of Agile. 

Consequently, the process was further refined by automating and streamlining the SDLC and incorporating Continuous Integration (CI). In CI, the code is tested repeatedly and integrated to create a stream of small but frequent releases. However, these challenged the Ops team, which found it difficult to keep pace with Development. So, while Agile addressed the issues developers faced with glitches being passed on to the next phase, the DevOps approach turned out to be more effective. It treated the entire SDLC as a monolith of collaborative processes that generate better outcomes.

Continuous Delivery and Testing

To support the strategic business needs, enterprises seem to have graduated from performing CI to implementing CD. In doing so, they have finetuned both processes and technical frameworks. So, from creating CI builds and executing testing to achieving deployment, the Continuous Delivery and Continuous Testing methodologies have covered all dimensions of the organization’s operations. These ensure the quick and frequent deployment of quality software applications to the end customers. The questions to be asked while implementing a continuous testing framework are:

• Is the software application deployable during its lifestyle?
• Can the software application be deployed while the team is working on its new features?
• Can the process receive quick and automated feedback each time a change is implemented?
• Can a push-button deployment be performed for a software version in any environment?

How does Agile, DevOps, and Continuous Testing benefit enterprises

These interconnected methodologies help enterprises in several ways.

• Accelerated time to market
• Better productivity and efficiency
• Frequent releases of reliable and stable builds
• Capability to build products aligned to the market
• Better feedback mechanism
• Superior customer experiences

Conclusion

The need for enterprises to be the disrupter in the market by producing or delivering top-quality software products or services has put focus on methodologies like Agile, DevOps, and Continuous Testing. The complementary relationship among the three methodologies has led to the overhauling of processes and working culture in favor of a new paradigm where quality deployment is a continuous process.

Article Source:

https://devops.com/

What are the various phases of an Agile Testing Life Cycle?

 

The agile testing lifecycle comprises the planning of a sprint, designing a test case framework, conducting actual testing, ensuring product stability, and executing regression testing.

The digital landscape of today has given enterprises the tools, technologies, and methodologies to achieve a slew of objectives. These include improving the quality of software applications according to the market demand, accelerating the time to market, taking quick decisions in real-time, and becoming competitive. Agile has been one such methodology that has enabled enterprises to streamline their development, testing, and deployment processes based on the ever-changing demands of the end customers. Its structured approach balancing quality and speed can deliver value to the enterprises and their customers.

The high point of Agile way of development and delivery is increased collaboration between processes. Here, development and testing are not mutually exclusive and siloed processes but part of a continuum called sprint. The agile testing approach allows development and testing to be conducted simultaneously and throughout the SDLC. Further, the testers are involved in gathering requirements thereby facilitating the creation of test cases. Agile testing also involves the running of regression tests whenever a new feature is integrated into the software application. Using the agile model of development-testing-deployment, the QA team bakes in code quality and achieves robust business outcomes.

What is agile testing all about?

To overcome the inadequacies of traditional ‘waterfall’ testing methodology, the cross-functional agile quality assurance process integrates testing into the development phase. As testing is conducted incrementally (and iteratively) and in real-time, both development and QA are able to communicate and exchange information about the hidden glitches in the code to get them fixed.

In agile test management, a sprint is created to conduct specific development and testing related activities to be reviewed later. The sprint begins with a meeting where the development and testing teams realistically finalize the tasks to be accomplished. Thereafter, daily meetings are held to discuss the progress of testing and solutions are arrived at post brainstorming to sort out any challenges.

Agile testing strategy – advantages

The benefits of following an agile testing strategy include

• The requirements and modalities of testing are discussed collaboratively as a team. This offers team members with better insights into the business and technical aspects of testing enabling better alignment.
• Each testing requirement is defined based on a metric, which is measurable. This allows the QA specialists to understand whether the task has been completed.
• Test estimates are not overlooked as the QA specialists participate in the planning phase within a sprint.
• Regression testing is executed by leveraging test automation.
• The overall quality of code becomes the responsibility of the whole team (development and QA) rather than that of QA alone. At the beginning of development (and simultaneous testing,) the whole team agrees to the test strategies, prioritization of tests, and test cases.

Decoding the lifecycle of agile testing services

Following is the workflow of agile quality assurance involving both developers and testers.

Planning of a sprint: A sprint constitutes the total time given to the team to complete a user story. Here, development and testing are divided into small iterative and incremental processes. At the beginning, the project owner, developers, and QA specialists discuss the objectives to be achieved and activities to be performed within the sprint. It also includes the daily stand-ups to plan the course of the day.

Designing a test case: While the developers build user stories, the QA specialists design the test cases. The latter include various tests, parameters, and metrics to be conducted/monitored. The initial design of a test case determines how the subsequent test cases would be. The same is then shared with the development team for review. Thereafter, both the teams decide on the test cases to be automated.

Actual testing: In an agile environment, the testing team tests the user stories that are created by the development team. By working in tandem, the teams are able to detect (and fix) glitches early in the product lifecycle. The automated test cases are executed across the development cycle and the defects are fixed therein.

Product stability: The best part of working in an agile environment is the ability to add new features to the product at any stage without making it complex. The agile testing team ensures product stability after determining the requirement flow.

Regression testing: Post addition of a new user story to the development process, both manual and automated test cases are run to understand the impact of the new user story on the functioning of the product.

Conclusion

Agile testing breaks the barriers between development and testing processes and helps to eliminate glitches from the software code early. It is certainly capable of addressing the myriad challenges of the modern software development process compared to the traditional waterfall model. 

Article Source:

https://www.sooperarticles.com/technology-articles/software-articles/decoding-agile-testing-life-cycle-1787797.html

Why it is important to transition from Quality Assurance to Quality Engineering?

 

The inscrutable march of technology continues taking convenience, quality, capability, scalability, and user experiences to a whole new level. Enterprises are looking at implementing new technological paradigms and tools to develop quality products and services, generate new revenue models, and stay competitive. As the technology landscape transforms at a rapid pace with the advent of technologies like Artificial Intelligence, Robotics, the Internet of Things, Predictive Analysis, Big Data, and many more, traditional models are no longer adequate. When the stakes are so high with driverless cars and IoT devices on their way to become the new normal, traditional software quality assurance services need to give way to quality engineering. 

The quality engineering approach is about driving quality into the core of any software development process rather than following it along the way. This helps to reduce the possibility of errors/bugs to get into the system. Thus, quality engineering is more of a pre-emptive way of reducing glitches and ensuring the applications running the IT ecosystems of tomorrow are of proven quality. Further, the below-mentioned developments or observations highlight the predicament of following traditional software quality assurance services –

• About 30 percent of glitches or defects are due to wrongly configured test environments (Souce: an IBM study)
• Poor quality software leads to a loss of $60 billion annually in the USA
• Enterprises can save costs by optimizing the use of tools (Source: Gartner)
• Software testing comprises more than 50 percent of the development cost. This calls for automating the QA process and improving its effectiveness (Source: Journal of Systems and Software)
• Actual resource utilization for testing is about 57 percent instead of the expected 75 percent (Source: NIST Journal)

Why transform from quality assurance to digital quality engineering?

The benefits of switching to a robust, all-encompassing, and qualitatively superior QE services are as follows:

Driving the DevOps pipeline: DevOps envisions the marriage of development and operations to improve the quality of products and customer experiences on a continuous basis. Software quality engineering envelops DevOps by bringing the management, ideation, design, systems, product management, and operations together. It is a holistic approach to develop and deliver software applications that are safe, reliable, robust, secure, and scalable.

Maximum test coverage: In enterprise quality engineering, the entire span of the value chain (requirement to delivery) is covered in testing. It includes both shift-left and shift-right approaches of QA wherein the former testing is incorporated in the build phase itself. While in shift-right, quality is built into the delivery phase with continuous releases to ensure user satisfaction. Thus, software QE services cover the entire span of the SDLC including aspects like setting up and managing the test environments.

Powering CI/CD: DevOps is about developing and delivering software involving phases like build, test, and deployment. Here, every code change based on feedback from the QA team leads to faster integration and delivery in a transparent manner. The endless loop of feedback, code change, integration, and delivery ensures a better quality of products for the customer. Also, with the blurring of lines among departments and the initiation of a change in culture, quality is not merely the responsibility of the QA team alone but every stakeholder in the SDLC.

Better planning: There may be times when QA specialists identify an issue in the code requiring significant rework. This would lead to cost escalation and stretch the turnaround time. On the other hand, quality engineering services help in better planning at the initial stage of ideation and product development. They provide better insights to recognize limitations surrounding product implementation early on. Thus, identifying the potential glitches early in the development process can add to significant savings on cost and time. 

Better communication: Digital quality engineering specialists can test a product like the end-users and draw traceability into the systems should some glitches be identified. Their knowledge about the whole span of product development, testing, and delivery, helps in understanding issues from the perspectives of the system and users. They can contribute to enhancing the processes within the SDLC for churning out top quality products at every stage and iteration.

Conclusion

With quality becoming the cornerstone of product development and ensuring competitiveness for an enterprise, the thrust is towards eliminating glitches during the planning stage only. This is why it is important to transition from QA to QE to facilitate quicker releases through the CI/CD pipeline and ensure superior customer experiences.

Article Source:

https://community.nasscom.in/

Top ERP Testing challenges faced by the Enterprises

 

 Enterprise Resource Planning (ERP) has become the cornerstone of achieving success in the competitive world of business today. An ERP software suite helps an organization to conduct its operations seamlessly by integrating the departments, branches, processes, and activities. The ERP software suite comprises multiple applications with the capability to collect, store, organize, and analyze data emanating from multiple processes and functions. It can be easily deployed on-premises or on-cloud depending on the business objectives. It can help organizations in optimizing costs, enhancing efficiency, better monitoring of resources, quicken decision making, and improving competitiveness.

However, not everything is hunky-dory with implementing an ERP software suite and may involve a few daunting challenges. The challenges can be attributed to poor management of the suite including inadequate training of the people using it. The people should have the expertise in conducting ERP testing to ascertain if the software suite is capable of meeting all business requirements. Further, testing ERP systems can bring out (and fix) the glitches or issues within the systems before they are deployed. Let us understand the main challenges testers face during ERP implementation.

Challenges for ERP application testing services

ERP can transform the manual operations of enterprises into digital and bring about transparency, speed, flexibility, accuracy, and convenience. However, any ERP software testing exercise can face a raft of challenges as:

Choosing the best ERP software suite: The market has many ERP systems with each claiming to be the best. This makes it difficult to choose one that suits your business requirements. So, at the outset of choosing an ERP software suite, find out the business requirements and how the ERP software could help addressing them. Further, the ERP software suite and its various applications should align with your business domain. Analyze the features of the suitable ERP software for your business and choose one with attributes like robustness, customizable, secure, and easy-to-operate.

Technical challenges: For proper ERP implementation, the entire system comprising software applications, databases, hardware, servers, network, and users should collaborate and work seamlessly. However, unless an enterprise is using a cloud-based ERP software suite, the hardware and servers may need to be changed. In addition, the speed and bandwidth of the internal network should be considered along with its interface with mobile devices. If these issues are ignored then there could be issues like latency or even system malfunction. Enterprises can weigh between implementing ‘as a service’ cloud-based or on-premises ERP systems for both can have their pros and cons.

Quality of data: The ERP implementation solutions can have compatibility issues with the data generated through legacy resource planning systems working within organizations. Thus, proper project planning should precede the implementation of any ERP centre of excellence. The planning would highlight the modifications the ERP system would need for its smooth functioning.

Adequate managerial support: An ERP software can trigger comprehensive changes in an enterprise’s traditional business model, practices, and operations. Also, the information keyed-in by one user in a process within the ERP suite may trigger an instant response in other processes in real-time thereby disrupting the entire ecosystem. And unless a change in the working culture of the organization is initiated from the top, the real benefits of implementing an ERP system may remain a distant dream.

Adequate training: The success of an ERP system would depend on the people using it. So, the employees should be adequately trained and motivated in operating the system. The ‘resistance to change’ among employees can be addressed by explaining the benefits of the system clearly. The managers may initiate ‘one-to-one’ communication in explaining how the system will make things easier and convenient for them. This will help employees to accept ERP validation for various operational aspects.

Inventory management: Zeroing on the perfect quantum of inventory can be tricky, for it could either be too less or too much for the organization’s requirements. So, it is important to consider the lead time wherein proper procurement of the inventory can be done in real-time instead of waiting until the inventory is exhausted in the warehouse. The ERP system can monitor the levels of inventory and let the management know once a shortage is noticed. For example, any shortfall in inventory should alter the status of sales by making it unavailable for any new requests.

Conclusion

Pulling off any ERP implementation and addressing the various challenges would entail detailed planning and monitoring. A proven approach to ERP testing including the conduct of due diligence is critical to streamline processes and achieve proper business outcomes. 

Article Original Source:

https://medium.com/@hemanthkumar989/what-are-the-main-challenges-faced-in-erp-testing-72e28ffc947a

Why is RPA so important for Mobile Testing?

 

The dominance of mobile phones as the preferred medium for accessing the internet is an established fact. This has created an app ecosystem where enterprises are competing among themselves to develop attractive, robust, customized, feature-rich, and secure mobile apps across verticals. Mobile testing has emerged as an integral part of this app ecosystem thanks to the rising cyber security challenges and fast-changing market dynamics. In fact, the criticality and complexity of mobile application testing are underpinned on the following criteria:

•  Testing of mobile apps should be done across browsers, operating systems, versions of operating systems, device platforms, and networks
• Quick release of newer OS versions and patches
• The varying hardware configuration of devices in terms of screen sizes, memory, processor speed, and others can be challenging
•  Unavailability of specific device platforms during testing
• Choosing a combination of devices, operating systems, and browsers to optimize testing
•  Availability of various categories of mobile apps – native, hybrid, and web and their need for testing

To address the myriad testing challenges, enterprises are increasingly veering towards adopting RPA (Robotic Process Automation.) If statistics are to be believed then the global RPA market is expected to touch $10.4 billion by 2023. Let us first understand what RPA is all about.

What is Robotic Process Automation or RPA?

It is an IT solution that lets enterprises automate many standard and mundane repetitive activities. Consequently, these activities are performed accurately and up to the desired expectations without any human intervention. It helps organizations to improve productivity, enhance efficiency, and accelerate a product’s time to market while upholding quality. RPA can be implemented in executing a plethora of tasks related to areas such as supply chain management, customer service, data analytics, and others. Its vast potential can only be achieved through meticulous planning.

When it comes to mobile testing, RPA can eliminate human errors and infuse reliability, accuracy, and transparency into the development and testing processes. It can easily scale the testing requirements, reduce the cost of testing, and take customer satisfaction to newer heights. Further, automated processes like RPA can significantly reduce the development and deployment lifecycle cost and duration of a mobile application. When a significant portion of testing is automated, the QA specialists will have the time and wherewithal to advance their skillsets and bring greater value to the business.

RPA helps enterprises in detecting anomalies in processes where anomalies are the outlier data patterns that do not seem to appear as normal. Such anomalies can constitute malicious codes to cause cybercrimes like data and identify thefts, data breaches, and malicious attacks, among others. To ensure that RPA performs its role in mobile app testing, enterprises should consider:

Processes to automate: It is not feasible to automate every process as there may be a need for human intervention. Besides, RPA can automate processes that are standardized, structured, and rule-based. So, the ones without standardization cannot lend themselves to automation.

Resources: There is a lack of trained resources for RPA given its relatively recent origins. To further add to the worries, there is a lack of availability of structured data across processes making the implementation of RPA and achieving accuracy a challenge.

Management approval: The implementation of RPA can cause disruption across the value chain due to its requirement for changes in the IT infrastructure of an organization. So, the management should approve of the implementation and oversee the disruption.

Benefits of implementing RPA in mobile application testing

RoboticProcess Automation can accrue a host of benefits for enterprises/developers/testers as mentioned below:

• Since RPA is run by specific tools, there is no need to remember any syntax.
• The QA team can create a test case by taking a simple drag and drop approach.
•  The capability of RPA testing of mobile applications can be enhanced by assigning specific jobs to different workstations.
• As a minimal workforce is needed, organizations can save significant costs on overheads.
• ince the process is executed by bots that follow a standardized approach, accuracy is assured.
•  Since there is no manual activity involved, testing can be carried out in non-stop iterations.
  
•  RPA can be flexible and does not depend on the type of testing – web-based or mobile-based. Moreover, it allows the parallel execution of tests.

One of the major challenges to testing mobile applications is managing the frequent updates and changes. So, by automating the repetitive tasks, enterprises can achieve efficiency and better detection of glitches. Also, since mobile test automation needs to be carried out on multiple platforms, virtualized devices or emulators can be leveraged. The implementation of RPA will have the below-mentioned features:

Total test coverage: RPA testing should be comprehensive and cover every aspect of development and testing – functional, non-functional, and integration.

Scriptless test automation: RPA does not need the human resource to have any programming skills. Any business analyst or Subject Matter Expert (SME) can learn to use the RPA tool. Since the bot can access the end-user system through a controlled user interface, there is no need to have any program to run the system.

Parallel execution of mobile automated testing: Customers are wont to use multiple mobile devices from different OEM vendors. And unless an application is tested across devices its quality is not validated. The RPA should ensure the parallel execution of app testing on multiple device platforms.

Continuous integration: The integration of various APIs should be properly verified.

Network testing: The functioning of a mobile application depends to a great extent on the available network. RPA testing should evaluate the mobile apps’ compatibility with different networks.

Security testing: One of the aspects of security testing is checking if the app adheres to the various security protocols and regulations. Also, since app stores will include an app only after ensuring it does not have any offensive data, prior testing should be conducted to verify the app’s adherence to all industry standards.

Conclusion

Leveraging the RPA tools can help enterprises in validating the quality of a mobile application across platforms. However, it should be done after meticulous planning to ensure efficiency. It is only by adopting the right approach for automation (web-based, cloud-based, and lab-based) that RPA can deliver the right outcomes.  

Article Original Source:

https://dev.to/cigniti/how-can-you-leverage-rpa-for-mobile-testing-3f32