Performance Testing HCL Commerce with HCL DevOps Test

As more and more business in both the B2B and B2C spaces is driven through digital commerce platforms, organizations must ensure their websites maintain the performance and reliability required to deliver great customer experiences. To that end, performance testing and monitoring should be conducted regularly using tools such as HCL DevOps Test Performance against the application.

Understanding the Complexity of HCL Commerce Performance

The HCL Commerce application is composed of several software applications and integrations, and performance issues can be complex and multifaceted. The hardware resources used to deploy the application are another factor to consider.

Defining Key Performance Indicators (KPIs)

Performance tests need to produce meaningful results that stakeholders can interpret. Some relevant and common key performance indicators commonly used for e-Commerce are, to name just a few:

• Order throughput

Orders processed per unit showcase the solution's revenue capacity. The test workload can be increased to determine whether a higher order throughput is possible without exceeding constraints such as response time and hardware resources.

• Response time

Response time directly impacts customer satisfaction and is inversely related to throughput.

• Page views

The number of page views is an indicator of how popular the website is, regardless of whether it generates revenue.

• CPU utilization, cache hit ratio, and database SQL activities

Some lower-level details, such as CPU utilization, cache hit ratios, and database SQL activities, are of interest to architects and developers who need to know what to modify to achieve better performance.

HCL DevOps Test Performance provides reports with these details, and they can also be customized to support problem determination.

Writing DevOps Test Performance scripts for Commerce requires not only understanding the basic steps of a simple shopping flow, like browsing to a product, adding it to the cart, checking it out and paying for it, but also the other flows that a shopper may go through while browsing on the storefront, like changing their shipping address, adding a new billing address, deleting items from the cart, and so on.

Once the script is written, you can define the volume of transactions to simulate a realistic customer workload, based on normal and peak business activity. This can be done in HCL DevOps Test Performance by changing the schedule properties and using user groups, random selectors, and other features discussed throughout this article.

There is, of course, much more to performance testing and to getting the best results with DevOps Test. To dig into the full details and learn how to do the testing right, read our e-guide!

Testing with HCL One Test Performance and HCL Commerce