I might have hurt the apps’ feelings with my title, but this is what this article is going to be about: stressing apps for results.
The results I am referring to are based on the speed, response time, stability, reliability, scalability, and resource usage of a software application under a particular workload.
That is what, in testing terms, we call Performance Testing.
To simplify this a bit, this is what we look for when testing performance:
Unlike regular testing, where the scope is to find bugs, for performance testing, our scope is to eliminate bottlenecks within our application.
The easiest and most common real-life example of this would be the Black Friday period. That is a moment when a large number of users (more than the regular amount) would access the same website at the same time. This kind of traffic overloads the servers and results in a broken website that would not load to any of the users, causing a so-called downtime that would make the company that owns the product lose a lot of money.
For example, in one of Amazon’s Web Service downtime, it was estimated that Amazon lost around 1100$ per second of downtime.
Based on what we actually need to track, we can go for one of the following types of performance testing:
How do you know you have found a performance problem and not a regular issue?
Well, some of the problems that we might encounter while testing the performance of an app are:
Glad you asked!
There are actually several tools out there that can help us analyze and see the performance of our apps. One of the most commonly used tools is JMeter.
Apache JMeter is an open-source, purely Java-based software. The software is used to perform performance testing, functional testing, and load testing of web applications.
With Jmeter, you can basically create a large number of users that perform a certain task through a so-called Thread Group. This way, you can simulate a heavy load and track the results of pretty much anything you need. Here, you can adjust the number of users, the loop count, and even the delay between users' actions.
And guess what? It is entirely free to use. There is no paid extra feature or something like that. However, you might not enjoy the interface as it can look a bit old school.
But trust me, once you get the hang of it, it does its job flawlessly.
JMeter does not leave you hanging when it comes to viewing the results, either.
There are 2 main ways that you can use to check and interpret the results.
Performance testing is an important process that every QA should incorporate into their skill set, as it is crucial to check how our apps behave in stressful situations before we launch them for the whole world to see.
Our end goal is to keep the user engaged by maintaining a “healthy environment” in our apps.
Remember that there are several tools out there that can help us with this process, so find one that better suits your project’s needs.
Stay up to date with the tech solutions we build for startups, scale-ups and companies around the world. Read tech trends and news about what we do besides building apps.