Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Nächste SlideShare
Agile scrum induction
Agile scrum induction
Wird geladen in …3
×

Hier ansehen

1 von 39 Anzeige

Weitere Verwandte Inhalte

Aktuellste (20)

Anzeige

JMeter_PPT.pptx

  1. 1. Performance Testing WHAT ? A non-functional testing technique performed to check speed, response time, reliability, scalability, stability of a software program under expected workload. It is a subset of performance engineering and is also known as “Perf Testing”. The focus of Performance Testing: 1.Speed/Response Time – Determines whether the application responds quickly. 2.Scalability – Determines maximum user load the software application can handle. 3.Stability – Determines if the applications is stable under varying loads.
  2. 2. Performance Testing WHY NEEDED? Performance testing uncovers what needs to be improved before the product goes to market. Without performance testing, software is likely to suffer from issues such as: 1. Running slow while several users use it simultaneously. 2. Inconsistencies across different operating systems and poor usability. 3. Bottlenecks are obstructions in system which degrade overall system performance. Some common performance bottlenecks are: - CPU utilization - Memory utilization - Network utilization - Disk usage
  3. 3. Performance Testing TYPES : 1.Load Testing: Applying desired number of load and checking the stability & response time of the application. 2.Stress Testing: Applying more then desired number of load and checking the stability time of the application. 3.Endurance/Soak Testing: To make sure the software can handle the expected load over along period of time. 4.Spike Testing: By increasing the number of users suddenly by a very large amount and measuring the performance of the system. 5.Volume Testing: Transferring/Write huge volume of data into db & monitor the stability & response time of application.
  4. 4. Performance Testing Performance or Load Testing Tools: When we have to measure the load, stability, response time of the application, we required some performance (load) testing tools, which help us to test the performance of the software or an application. There are various types of performance testing tools available in the market; some of the most used performance (load) testing tools are as follows: - Apache Jmeter - LoadRunner - LoadNinja - NeoLoad - LoadView etc.
  5. 5. WHY ? 1. Its is open source tool. 2. It can load & perform test many different server types: - Web -HTTP,HTTPS - Web Services - SOAP - Database via JDBC drivers - Messaging Oriented service via JMS - Mail Service − POP3, IMAP, SMTP - FTP Service 3.It allows concurrent sampling by many thread groups. 4.Test results can be captured in various format like summary report,graph,results in tree & table,etc. About Apache JMeter
  6. 6. About Apache JMeter How JMeter works?
  7. 7. About Apache JMeter Installing & Configuring Jmeter : 1.Install Java : - Your PC might already have java installed on your system, if not just install it from the website. - Check your java version: go to cmd and type java -version(v).You Will get something like this:
  8. 8. About Apache JMeter Installing & Configuring Jmeter 2.Download Apache JMeter : - Download jmeter from below link https://jmeter.apache.org/download_jmeter.cgi - This will download a zip file.Unzip this to a directory. - Start Jmeter from Terminal/cmd. a. Traverse to the jmeter installed path, for my case this is: ”/home/deepali/Downloads/apache-jmeter-5.5/bin” b. And run Jmeter.sh (for Linux)/Jmeter.bat(for Win) c. This will open the GUI of Jmeter.
  9. 9. Concepts in Apache JMeter 1. How to prepare a Test Plan in Jmeter. 2. How to prepare Test script in Jmeter. 3. How to put load & analyze performance metrics. 4. Importance of HTTP Cookie Manager. 5. Assertions 6. Controllers 7. Timers 8. Correlation 9. Data Drive Testing in Jmeter
  10. 10. What is Test Plan ? - A Test Plan describe a series of steps jmeter will execute when run.A complete test plan will consists of one or more Threads group, logic controller, listner, timers, assertions, and config elements. - The different components of JMeter are called Elements. Each Element is designed for a specific purpose. Elements in Jmeter or in a Test Plan
  11. 11. Thread Group - Setup numbers of threads - Setup ramp up period. - No. of times test execute. Controller - Samplers(Send reuqest to server) - Logical controller(customize logic to send request) Listener - Graph Results - View results tree & many more Timers - Delay next request certain amount of time. Assertions -Allow you to assert fact about response received from HTTP request Elements in Jmeter or in a Test Plan
  12. 12. Subject lines : ● Dont ignore it. ● Aim for under six words ● Avoid vague words like ○ ‘Hello’ ○ ‘Update’ ● Front - loaded keywords ○ Keep Words like ‘ Project Zeus: Update ‘ not ‘Update on Project Zeus’ About Apache JMeter
  13. 13. When to flag urgent emails : ● Only use the high priority flag when you need someone to take an action to avert an imminent disaster such as huge financial losses , law suits or reputational scandals. Why NOT to flag : ● Overuser may irritate your colleagues. ● If something’s urgent or important, say so in your subject line. About Apache JMeter
  14. 14. ‘TO’ , ‘Cc’ , ‘ Bcc’ , ‘ Reply all’ : When to use the ‘To’ Field: People directly affected by your email, such as when: ● You want them to do something. ● You are replying to their message. ● They are named in your greeting. About Apache JMeter
  15. 15. When to use the ‘Cc’ Field: ● Use this field when you are not expecting the recipient to take any action in response to your email. When NOT to use the ‘Cc’: ● Informal escalation ● Powerplays ● Back-Covering About Apache JMeter ● Thumb Rule :A good rule of thumb is to announce your use of the Cc to the email’s main recipient - i.e.,by saying something like : ‘I am cc’ing my colleague Dave, who’ll be handling the design for the project.’
  16. 16. When to use the ‘Bcc’ Field: ● When people should not be able to see teh email address of all the other recipient. ● When you want to Bcc your own manager or your HR team to keep them in the loop without alarming the employee. Danger of using ‘Bcc’ : ● Recipient may respond with ‘Reply all’ - fwd the original message to the third party after you have sent it instead. Email Etiquette ● Thumb Rule :If sending a Bcc makes you feel abit gulity, sneaky or mean, don’t do it!.
  17. 17. Sending attachments - best Parctice ● Attach it before you begin writing the email. ● Mention that you have attached it in the body of the email. ● Keep file size under 5MB. ● Zip it or use a file transfer service if the file is above 5MB. ● Watch your format.Use universal file types like .PDF, .RTF, and .JPG. ● Group attachments in separate emails. Email Etiquette
  18. 18. Out-of-office messages : ● Be specific with dates ● Checking in? Mention, but manage expections. ● Provide your contact details if you are happy to be contacted. ● Put them in touch with a colleague. ● Keep it professional!. Email Etiquette Remebmber! : ....to turn your automatic reply off as soon as you get back to the office !
  19. 19. Proofing and polishing : how to avoid email errors - ● Fill in the ‘To’ field last. ● Cut and paste from word. ● Check their name - always! ● Check subject lines, dates, times, hyperlinks and attachments separately. ● Use automatic spell check. ● Print it out - and enlist a colleague’s help. Email Etiquette
  20. 20. Now There are Total 7 Steps We need to follow for writing an effective emails : 1. Ask yourself : ’Is email the best channel?’. 2. Add attachments first. 3. Craft your message using the SCRAP structure. 4. Add some white space. 5. Writeyour subject line. 6. Proofread 7. Insert Addresses. Email Etiquette
  21. 21. Assign Tasks in an Email Using the “3Ws”: 3Ws : Who, What, and When - every action should have a clear Who, What, When. 1.Who - Name of a specific person who you want to complete a task for you(not a group of people). 2.What - Description of the exact task you need someone to do (no assumptions). 3.When - Exact date and time a task needs to be completed by (clear deadline). Ex.”Ray, please send me the updated status report by Monday,Nov 23 at 3pm US Eastern Time”. 2. Write Better Emails
  22. 22. Write the perfect Subject Line : ● Summarize the 3Ws (your Email). ● Use Prefix modifiers. ● Change the subject line only when the subject changes. Write Better Emails
  23. 23. Write Emails that are 5 sentences or less - TL;DR : ● Know what you really want first. ● Get to the point immediately then. ● Hightlight a lack of required response. eg.’FYI’, ‘NNTR’ or ‘No Action Needed’. Write Better Emails
  24. 24. Break Long Emails into Two parts : ● Quick Summary - Keep this part 5 sentences or less. ● Details - Elaborate on the summary. Write Better Emails
  25. 25. Make you Emails Scannable : ● Use Bullets points for all your actions and questions ● Use Sub-headings, white spaces, highlights and/or bold text Write Better Emails
  26. 26. Show by Attaching Screenshots Instead of Tell: ● Use screenshots to save time and improve clarity. Ex. : Give someone instructions or highlight slide in deck. Write Better Emails
  27. 27. Spell out Time Zones, Dates, and Acronyms : ● Mention the exact time zone, day, and date. ● Ex.”How about tomorrow,Friday, Aug 5, 2022 at 9:30am US Eastern Time?” ● Do the Same for acronyms. ● Spell out acronyms at leadt once in an email. Write Better Emails
  28. 28. Use “If..then...” Statements : ● For increasing accountability, clarify expectations, for reminders and reduce the amount of follow-ups. Write Better Emails
  29. 29. Present Options Instead of asking Open- Ended questions: ● Present clear options ● Give alternatives when scheduling meetings ● Example : State “Do you think we should do A, B or C?” instead of “What do you think about this?” Write Better Emails
  30. 30. Re-Read Your Email once for a Content Check : ● Re-read your entire email from top to bottom. ● Re-reading the questions as well as the answers helps ensure that your responses make sense before you reply. Write Better Emails
  31. 31. Save Drafts of Repetitive Emails : ● Use a template for weekly and monthly status calls. ● Save drafts based on client or topic. ● A standard format improves communication with your team members. Write Better Emails
  32. 32. Write it Now, Send it Later Using Delay Delivery : ● Use delay delivery feature to send emails when they are most likely to be read. ● Use delay delivery as a reminder tool. Write Better Emails
  33. 33. Don’t Reply All (Unless you Absolutely have to) : ● Don’t use reply all when only the original sender needs to read your message. ● Send a follow-up ‘reply all’ email after any offline discussions. ● Mention when you are removing members from the reply all list. ● State that what you want your recipients to do at the end of your email. Write Better Emails
  34. 34. Reply to Questions Inline : ● List questions on seperate lines and if the questions were not sepearted out, then do that yourself. ● Use a different color font. ● Copy the original questions in your reply. Write Better Emails
  35. 35. Reply Immediately To Time-Sensitive Emails : ● Make sure the acknowledgments is meaningful instead of just saying “OK”. ● Spell out your need for an acknowledgment. ● Ex.”Please confirm that you received this email and that you will get this done.” Write Better Emails
  36. 36. Read the Latest Email on a Thread Before Responding : ● Sort your email messages by subject line. ● Can also use “Conversation threading” where messages with the same subject line are visually grouped together. ● If you make a mistake, correct it by replying back to the team. Write Better Emails
  37. 37. Write the perfect Out-of-Office (OOO) Auto Reply : ● Include everything your recipient needs to know while you are away. ● State the exact dates, hightlight your backup contacts, and set the right expectations. Write Better Emails
  38. 38. Share the Rules of Email Ahead of Time : ● Set up a short meeting with your team and make sure everyone agrees on email best practices ahead of time. ● Be flexible on the rules. ● Use what you like, delete what you don’t, and add any new ones that apply to your team. ● Establish ground rules so that everyone communicates more effectively. Write Better Emails
  39. 39. Cover in earlier Slides. 3.Email Writing Thank You!!!

×