#AskRaghav

[@rahilchaudhary462]

Well said Raghav. One Input. Performance Plan: for server side performance: We need to be vary of the apis that involve cost. we suffered while doing performance testing for a scenario which was hitting a costly third party api it ended up blowing organization's budget and the performance team was pulled up for this.

[@RaghavPal]

Very valid point Rahil, I missed it, will add in description. Have pinned your comment.

[@awkward216]

Thanks for sharing a valuable notes. I need your help to understand for initial requirements and report. It would be great if you can share or give detailed report session. How we can create and which type of details need to record like that.

[@RaghavPal]

Sure, I will make a session on this

[@vikumravinayake1882]

Really informative, Learned many things in a moment of struggling without any idea of how performance testing is going on. Thank you, Raghav 👌🤝

[@RaghavPal]

Most welcome Vikum

[@rojakadaveru8848]

From where I can get best real time projects to practice scripts for performance testing

[@RaghavPal]

Can check some github projects

[@RAVIKUMAR-ys9sh]

grt explanation thank you sir can you plz explain how to show performane testing report how its looks like and how use ful/benefit for testing team

[@RaghavPal]

I will do a session on this Ravi

[@vishnucharan3840]

can you explain, What are the metrics we analyse in each of the tests (Load, Stress, Endurance, Spike, etc..). with the help of realtime project.

[@RaghavPal]

Will do a session on this Vishnu

[@prithvivishwanath]

Hi Raghav, Best Online Mentor 🙏 Raghav Thanks for sharing PT videos in your channel .. I have one question please please answer me i am so confused in my future. I have currently working as Performance Tester , i have 10 years of experience where 5 years in PT and 5 years in Functional tester . Now i wanted to learn some advance course . considering this i wanted to learn Is both PT and Security testing have a future atleast for another 5 years to survive ? Or

[@RaghavPal]

Prithvi Let's explore the future prospects for both Performance Testing (PT) and Security Testing. 1. Performance Testing (PT): - PT remains crucial in ensuring that software applications perform well under various conditions. Here are some trends to consider: - Performance Engineering: Performance Engineering is replacing traditional Performance Testing. It focuses on consistent performance across diverse platforms, operating systems, and devices. A good user experience is essential for a successful product, and PT plays a vital role in achieving that - Quality@Speed: Organizations want both speed and quality. As technologies evolve, expectations for faster delivery and better quality will continue to rise. PT will remain relevant in achieving this balance. - Software Development Engineers in Test (SDETs): SDETs, who specialize in test automation, will continue to be in demand. Many testers will need to wear an SDET hat to succeed in the field of Test Automation. - Agile and DevOps: These methodologies will continue to dominate. Organizations will focus on centralized and well-governed testing to achieve greater quality. 2. Security Testing: - Security testing is critical in today's digital landscape. Here are some trends: - Digital Transformation: Organizations must embrace digitalization. Security testing will play a significant role in ensuring the security of digital assets. - Big Data Testing: With explosive amounts of data, robust strategies for Big Data & Analytics Testing are essential. Security testing will be crucial in optimizing functional testing across channels. - Supply Chain Security: The focus will shift toward identifying security vulnerabilities in the supply chain. - Social Engineering: As cyber threats evolve, social engineering testing will remain relevant. In summary, both PT and Security Testing have promising futures. Continuous learning and staying updated with industry trends will be essential for your career growth. Consider exploring certifications or specialized courses in these areas to enhance your skills and stay competitive. Best of luck

[@prithvivishwanath]

@@RaghavPal thank you so much Raghav for detail explanation 🙏🙏🙏🙏

[@NeetuGokhe]

Can you pls create a tutorial on Locust performance tool.

[@RaghavPal]

I will plan Neetu

[@ankitasalvi8222]

can you please help us to know the major issues faced during performance testing and how you have fixed them? also different scripting issues and solutions.

[@RaghavPal]

Sure, will do Ankita

[@saikrishna-wh5dl]

Sir how to setup the test environment and how to prepare report the results from base line test to load test with 100users a clear cut video for us.

[@RaghavPal]

Sai To setup the test environment for a load test with 100 users, you will need: * A load testing tool, such as JMeter or LoadRunner. * A server or cluster of servers that can handle the load of 100 users. * A test script that simulates the actions of 100 users. Once you have the necessary resources, you can follow these steps to setup the test environment: 1. Install the load testing tool on the server or cluster of servers. 2. Create a test script that simulates the actions of 100 users. 3. Configure the load testing tool to run the test script with 100 users. 4. Run the test. To prepare a report of the results from the baseline test to the load test with 100 users, you will need to collect the following metrics: * Response time: The time it takes for the application to respond to a request. * Throughput: The number of requests that the application can handle per second. * Error rate: The percentage of requests that fail. You can use the metrics to compare the performance of the application under baseline conditions to its performance under load conditions. This will help you to identify any performance bottlenecks that may occur when the application is under load. Here are some additional tips for preparing a report of the results from the baseline test to the load test with 100 users: * Include a summary of the test configuration, including the number of users, the duration of the test, and the metrics that were collected. * Identify any performance bottlenecks that were identified. * Make recommendations for improving the performance of the application. I hope this helps

[@BenjaminYadav]

#AskRaghv Hi raghav I have been ask this question in one of interview. what will you do , If everything this upto date in jmeter like Certificate, proxy settings and still jmeter is not able to record the script? Also what are the ways to record the script in Jmeter? Could you please make a saperate video on this?

[@RaghavPal]

Hi Swapnil I will plan for a video on this. Just for now: If JMeter is not able to record the script despite everything being up to date, there are a few things that can be done to troubleshoot the issue: Check the JMeter log file for any error messages. The log file can be found in the /bin directory of the JMeter installation. Make sure that the JMeter proxy settings are configured correctly. The proxy settings can be found under the "HTTP(S) Test Script Recorder" element in JMeter. Try using a different browser to record the script. JMeter may not be compatible with some browsers, so switching to a different browser could solve the issue. Use the JMeter "Template" feature to manually create the script. This involves creating HTTP requests and specifying the parameters and headers manually. There are several ways to record a script in JMeter: HTTP(S) Test Script Recorder: This is the most commonly used method. It involves setting up a JMeter proxy server, configuring the browser to use the proxy server, and recording the HTTP requests and responses. JMeter Chrome Extension: This is a Chrome extension that allows you to record HTTP requests and responses directly in JMeter. BlazeMeter Chrome Extension: This is a Chrome extension that allows you to record HTTP requests and responses and automatically generates a JMeter script. Badboy: This is a tool that allows you to record HTTP requests and responses and generates a JMeter script. Fiddler: This is a tool that allows you to capture HTTP traffic and export it to a JMeter script.

[@BenjaminYadav]

@@RaghavPal thanks a lot raghav

[@abhishekkr9712]

Handling "Captcha" is the biggest challenge anyone faced in performance testing.

[@RaghavPal]

It can be disabled for performance testing

[@BenjaminYadav]

#AskRaghav Hi Raghav, What are the ideal day to day responsibilities of performance test engineer?

[@RaghavPal]

Hi Swapnil The day-to-day responsibilities of a Performance Test Engineer can vary depending on the organization and project requirements. However, here are some common tasks and responsibilities: 1. Test Planning: Collaborate with stakeholders to understand performance testing objectives, define performance test plans, and determine the scope and test scenarios. 2. Test Design: Design performance test cases, including workload models, transaction volumes, and response time goals. Identify key performance metrics to measure and monitor. 3. Test Environment Setup: Configure test environments, including servers, databases, network settings, and performance testing tools. Ensure the test environment accurately reflects the production environment. 4. Test Scripting: Develop performance test scripts using appropriate tools or scripting languages. These scripts simulate user interactions and generate load on the system. 5. Test Execution: Execute performance tests according to the defined test plan and scenarios. Monitor system performance, collect performance metrics, and analyze test results. 6. Performance Analysis: Analyze performance test results to identify performance bottlenecks, resource utilization issues, and scalability limitations. Collaborate with developers and other stakeholders to troubleshoot and resolve performance issues. 7. Performance Tuning: Identify performance improvement opportunities and suggest optimizations to enhance system performance. This may involve tuning application configurations, database queries, or server settings. 8. Reporting and Documentation: Prepare performance test reports, documenting test results, analysis findings, and recommendations for performance improvement. Communicate test findings to project stakeholders. 9. Test Automation: Identify opportunities for automating performance tests and develop performance testing frameworks or scripts to improve efficiency and reusability. 10. Continuous Learning: Stay updated with the latest performance testing techniques, tools, and industry trends. Continuously enhance technical skills and knowledge related to performance testing. 11. Collaboration: Collaborate with cross-functional teams, including developers, architects, system administrators, and business stakeholders, to ensure performance requirements are understood and addressed throughout the software development lifecycle. Remember, these responsibilities may vary depending on the organization's specific needs, project complexity, and team structure.

[@BenjaminYadav]

@@RaghavPal Thanks for the response Raghav

[@sahulegendkiller]

Waiting for HP load runner tutorial

[@RaghavPal]

I will plan Sahu