What questions should we ask before starting performance testing?

Performance testing is little complex need lots of data before we initiate performance testing.

when you start out  Performance Testing can be overwhelming to figure out what you need to do and how to approach things. The best way to learn things is to just ask.

Question 1. 

Why do you want me to do performance testing?

 Before doing any kind of testing, we need to understand the business need for it. In order to define a test that gives back actionable information, we need to know why we are doing this test in the first place.What good is going to come from it?

Why are we running this performance test? This'll help you figure out what loads you might need to generate. And from there that gets you to the next question, which is, What tools do I have available to use? There's a lot of testing tools out there, and performance testing is no different. There's quite a wide variety. Some of the tools are free, and some of them are paid. But once you understand the why of your performance testing you can figure out which tools are actually going to help you accomplish the things that you need to do. You'll need to look at what tools are out there. And consider things like what budget you have and what tools your company might already have access to when trying to figure out what tools to use for the test that you're going to run. 

Now, another question that is good to ask early on in a performance testing project is, How can I get the data that I want? 

When we're setting up tests we need two kinds of data for performance testing. We need the input data that allows us to design the test that we want. So we need to have some way of knowing what kind of load we're going to generate. And that can partly be determined by the why of our testing, and also by understanding the loads on our system. 

But we also need access to the output data. We need some way to get data that lets us decide and know, if our test has passed or failed. Maybe we need server logs from the file.

What is Dev Ops ?

I believe most of us knows now what is Dev OPs and how much Dev Ops culture is valuable . For those who still have question about Dev - Ops ,  below definition might be helpful .

Dev-Ops is the way of thinking, applied in different types of organizations.

The forefathers of DevOps gave us a great acronym to use when defining DevOps:

C-A-M-S, or cams, which stands for culture, automation, measurement, and sharing.


Culture is the result of the way that teams interact.

In DevOps culture, the aim is to have development and operations teams interact in a way that breaks down barriers between the teams and with a clear focus on the roles and responsibilities of each.

With both teams working towards a common goal,everyone wins.

Automation is used to speed up the feedback between teams.

By using tools that enable collaboration and repeatable processes,interaction between development and operations teams can be easily facilitated.

This builds confidence in both teams' ability to successfully deliver a product or solution.

Some key points for automation include revision control with pull requests,continuous integration, and configuration management. 

Measure is used to track improvement. By measuring aspects of development and operations,teams can start to see where there are bottlenecks and take actions to improve them.
For Example Measuring the performance of production systems 

This helps teams to know that deployments have not degraded anything like response time, for example.

Sharing
Sharing allows for cross-pollination of ideas, problems, and solutions between various teams.And not just in development and operations,but throughout the entire organization.

By transferring knowledge, the collective intelligence increases and benefits everyone.

It also contributes to diversity of thought,transparency, and openness, which makes for teams that are more effective.