What is 'Shift Left Performance Testing'

This Article explains importance of Shift left performance testing, how to develop the mindset among the team and approach.

Video with detailed explanation —?https://youtu.be/DldAWXkM4tU

Connect with Author —?www.dhirubhai.net/in/vivekbasavegowdaramu

1. Introduction

A shift-left performance testing is a strategy where performance testing is conducted when components are being developed instead of waiting till the end where all components are developed and functionally tested.

Usually, performance testing is planned at the end of the testing cycle resulting in a stringent release timeline. If any performance issues are found then it leads to debugging time and efforts, thus reducing the overall development velocity, and increasing the cost

2. Shift-left Mindset

Having a positive mindset from the team is very important, early performance feedback will only increase efficiency and faster time to market.

Developers can gain early insight into performance degradation they’ve introduced in recent code commits

3. Approach

- Performance evaluation will happen in parallel to development

- Continuous feedback on performance improvements and fixes

- UI level performance evaluation for single use to fix issues early

- Frequent meeting with stakeholders to discuss on the report

3.1 UI performance evaluation

Many UI page evaluator tools are available in market, due to the easy of accessibility and to use in “optum.com” website — Lighthouse will be used for reporting and analysis

Lighthouse:

An open-source audit tool for improving the performance, quality, and correctness of web applications

3.2 Service Virtualization

- Service virtualization tools address the missing components of monolithic applications in the early stages of shift-left performance testing

- Service virtualization is a technique used in testing to simulate the behavior of components that might be unavailable or yet to be developed

3.3 Shift Left Load Testing

- Performance test scripts to be developed for the component which is ready

- Limited load or full load to be executed to test performance

- Enhance script and include newer components as development progresses

4. KPI`s

Unlike regular performance testing here main focus is on meeting the SLA and ensuring application server metrics are within threshold etc

In Shift left performance testing, below Key performance Indicators are in focus

- Single user response time

- Page rendering time

- Data related errors

- Application-level errors/failures

- High running SQL queries

- Text compression enhancement

5. Reporting

Comprehensive performance report should be created highlighting the areas where issues are observed and with possible suggestions to implement fixes.

Further discussion with stakeholders should be planned to brainstorm fixes, implementation strategy and re-testing timeline

Sample Lighthouse report snapshot

6. Benefits of Shift Left Performance Testing

• Enable effective Agile approach
• Higher Efficiency
• Reduce cost
• Reduce re-work
• Higher velocity

Hope this was helpful and you learnt something today, good day :)