Performance Testing

The user experience and performance of a web application are equally important as functionality. Ensuring that the response time of any web application transaction is reasonable across mobile and web platforms, including when the load on the back-end servers is growing, should be part of any web application testing plan. There are leading performance testing frameworks on the market, such as JMeter (open source) with its supported load-testing product BlazeMeter and NeoLoad from Tricentis. From the perspective of the four main JavaScript testing frameworks covered in this course, most can offer measurements of transaction timing or, through browser developer tools (such as the CDP), utilize the Lighthouse tool to perform some advanced measurements of such transactions. Keep in mind that none of these frameworks comes with built-in load-testing capabilities.

Cypress performance testing

In most of the test automation frameworks that we’re evaluating here, Google Lighthouse can be utilized to measure the following top six key performance indicators:

• First Contentful Paint (FCP)

• Largest Contentful Paint (LCP)

• Speed index

• Time to Interactive (TTI)

• Total blocking time

• Cumulative Layout Shift (CLS)