The Power of Continuous Performance Testing: A Shift-Left and Shift-Right Approach

no stress we have CPT

In today's fast-paced digital world, the performance of a system can make or break the user experience. Whether it's a website, mobile app, or software application, users expect lightning-fast response times and seamless functionality. As testers, it's our job to ensure that these expectations are met, and one of the most effective ways to do that is through Continuous Performance Testing (CPT). I want to create a blogpost about CPT, which is the main idea of my talk given at ISTSTC-2024. You can reach to my presentation here as well.

What is Continuous Performance Testing (CPT)?

CPT is an approach to testing that involves testing the performance of a system continuously, from the early stages of development to after deployment. It's a shift-left and shift-right approach that enables teams to identify and fix performance issues early on, reducing the risk of downtime, crashes, and other performance-related problems.

CPT is a game-changer in the world of software testing. It involves testing the performance of a system continuously throughout the development lifecycle, rather than waiting until the end to run a few isolated tests. This shift-left approach allows us to catch performance issues early on, when they are easier and cheaper to fix.

But CPT is not just about catching bugs. It's also about optimizing performance and ensuring that the system can handle the demands of a growing user base. By running performance tests continuously, we can identify potential bottlenecks and scalability issues before they become a problem, allowing us to make adjustments and improvements proactively.

monitoring the performance of a system

The Importance of CPT

The traditional approach to performance testing typically involves testing towards the end of the development cycle, which can lead to:

Delayed detection of performance issues, resulting in costly rework
Longer development cycles, leading to delayed time-to-market
Poor user experience, resulting in lost revenue and reputation damage

In contrast, CPT enables teams to:

Identify performance issues early, reducing rework and saving time
Improve system performance, resulting in faster response times and better user experience
Reduce the risk of performance-related problems, leading to increased reliability and uptime

How CPT Works

CPT involves integrating performance testing into the Continuous Integration/Continuous Deployment (CI/CD) pipeline, allowing teams to test performance continuously throughout the development lifecycle.

Here's how it works:

Automated Testing: Automated performance tests are integrated into the CI/CD pipeline, allowing teams to test performance continuously.
Early Detection: Performance issues are identified early, allowing teams to fix problems before they become critical.
Continuous Monitoring: Performance monitoring tools are used to track system performance in real time, enabling teams to identify issues as they arise.
Proactive Improvement: Performance data is used to optimize system performance, ensuring that the system can handle increasing loads and user traffic.

Benefits of CPT

The benefits of CPT are numerous, including:

Improved System Performance: CPT enables teams to identify and fix performance issues early, resulting in faster response times and better user experience.
Reduced Risk: CPT reduces the risk of performance-related problems, leading to increased reliability and uptime.
Cost Savings: CPT reduces the cost of fixing performance issues, as problems are identified and fixed early on.
Faster Time-to-Market: CPT enables teams to release software faster, as performance issues are identified and fixed earlier in the development cycle.

Conclusion

Continuous Performance Testing is a game-changer for teams looking to deliver high-performing systems that meet the demands of modern users. By adopting a shift-left and shift-right approach to performance testing, teams can ensure that their systems are fast, reliable, and scalable. So why wait until the end to test performance when you can do it continuously with CPT?

Comic: https://images.app.goo.gl/TVy8DzqnVN4NhCHA8

Selenium Error "Element is not currently interactable and may not be manipulated"

Selenium webdriver can drive different browsers like as Firefox, Chrome or Internet Explorer. These browsers actually cover the majority of internet users, so testing these browsers possibly covers the 90% of the internet users. However, there is no guaranty that the same automation scripts can work without a failure on these three browsers. For this reason, automation code should be error-prone for the browsers you want to cover. The following error is caught when the test script run for Chrome and Internet Explorer, but surprisingly there is no error for the Firefox. Selenium gives an error like below: Traceback (most recent call last): File "D:\workspace\sample_project\sample_run.py", line 10, in <module> m.login() File "D:\workspace\ sample_project \test_case_imps.py", line 335, in login driver.find_element_by_id("id_username").clear() File "C:\Python27\lib\site-packages\selenium-2.35.0-py2.7.egg\selenium\webdriver\r

Change Default Timeout and Wait Time of Capybara

One of the biggest challenge for automation is handling timeout problem. Most of the time, timeout is 60 seconds but it may sometimes not enough if you have badly designed asynchronous calls or the third party ajax calls. This makes handling timeout more complex. set large enough to tolerate network related problems. For Selenium based automation frameworks, like Capybara, default Webdriver timeout is set to Net::ReadTimeout (Net::ReadTimeout) Changing ReadTimeout If you have timeout problem for Capybara, it gives an error like above. This means that the page is not fully loaded in given timeout period. Even you can see that page is loaded correctly but webdriver wait until the Ajax calls finish. class BufferedIO #:nodoc: internal use only def initialize (io) @io = io @read_timeout = 60 @continue_timeout = nil @debug_output = nil @rbuf = '' end . . . . . def rbuf_fill beg

Create an Alias for Interactive Console Work: Selenium and Capybara

If you are working on shell most of the time Aliases are very helpfull and time saving. For testing purposes you can use Alias for getting ready your test suites. In this post, I want to explain both running Selenium and Capybara on console and creating aliases for each. This post is for Windows machines, if you are using Unix-like see this post . Creating Scripts for Selenium and Capybara First of all, it is assumed that you have installed Selenium and Capybara correctly and they work on your machines. If you haven't installed, you can see my previous posts. I am using the Selenium with Python and the Capybara with Ruby. You can use several different language for Selenium but Capybara works only with Ruby. Create scripts in a directory called scripts (in your home folder, like as ~/scripts ) for your automation tool as following, save them as capybara.rb, sel.py : Creating Aliases Depends on your favourite shell, you need to add the alias to .bashrc bash

Page-Object Pattern for Selenium Test Automation with Python

Page-object model is a pattern that you can apply it to develop efficient automation framework. With the page-model, it is possible to minimize maintenance cost. Basically page-object means that your every page is inherited from a base class which includes basic functionalities for every page. If you have some new functionalities that every page should have, you can simple add it to the base class. Base class is like the following: In this part we are creating pages which are inherited from base page. Every page has its own functionalities written as python functions. Some functions return to a new page, it means that these functions leave the current page and produce a new page. You should write as much as functions you need in the assertion part because this is the only part you can use the webdriver functions to interact with web pages . This part can be evaluate as providing data to assertion part. The last part is related to asserting your test cases against to the

Performance Testing on CI: Locust is running on Jenkins

For a successful Continuous Integration pipeline, there should be jobs for testing the performance of the application. It is necessary if the application is still performing well. Generally performance testing is thought as kinds of activities performed one step before going to live. In general approach it is true but don't forget to test your application's performance as soon as there is an testable software, such as an api end point, functions, and etc. For CI it is a good approach to testing performance after functional testing and just before the deployment of next stage. In this post, I want to share some info about Jenkins and Locust. In my previous post you can find some information about Locust and Jenkins. Jenkins operates the CI environment and Locust is a tool for performance testing. To run the Locust on Jenkins you need command line arguments which control the number of clients , hatch rate, running locust without web interface and there should be so

TEST THE RISK!

Search This Blog