Performance Testing of an Application

We will try to figure out how our application works in load. We will look at the stability and response of our application so that stability and response time changes in load, we will test the behaviors in load.

Each app has its own limits, you should decide before you build it, my application is 1k req for 1 minute, this is your architecture limit.

• Load Testing

Let's assume you developed your application for 100 users in a moment, so you will test your app with 90–100 users in your test tool, not more than this because you will achieve the response time of planned working behavior. Achieve the response time. let's assume you get 2 seconds. We will use this number for other tests.

• Stress Testing

If you want to check how many requests and users can consume your application in 2 seconds(response time of load test), you will create a stress test for it, and then you will try to find what is the maximum user and request count, when you start to get response time over 2 sec that means you are over the stress, this limits will show you to not normal time times you application in stress moment, and you know how many of it can stand.

• Scaleability Testing

In this step, you will test when your application stops responding to requests. Regardless of whether your application runs on Docker or Kubernetes or IIS or in whatever environment, we will test how much load it cannot respond to and the server goes out of service.

• Volume or Flood Testing

The volume test is you will try how many files you can upload, you will check the bandwidth, will check your DB and your server what kind of thing can you upload, try it and see the limits of your server

• Soak or Endurance Testing

In this step you will put the load on your server and leave it, not like for a moment or 15–30min tests, put your load and leave it for 16 hours or 24 hours as much you want, check your endurance.