Users care as much about how your service performs as they do what job it helps them accomplish. This is why performance is imperative and performance testing a must. So why do we still see so many 503 errors and slow apps? The answer is empathy, a lack thereof. Performance is the most tangible element of “non-functional” quality criteria we regularly ignore until it’s too late.
You are the Selenium master and automate tests in your sleep. You make sure the quality of your companies web page is 100%. But then the team wants you to measure the performance of your site. How do you do that? Is that even possible to measure web performance with Selenium?
Apache JMeter is one of the most well known open source tool that can be used to perform load testing or functional testing. The book Performance Testing with JMeter 2.9 written by Bayo Erinle provides you with the knowledge to start using JMeter and the basic concepts for successful performance testing.
The performance of your application affects your business more than you might think. Top engineering organizations think of performance not as a nice-to-have, but as a crucial feature of their product. Those organizations understand that performance has a direct impact on user experience and, ultimately, their bottom line. Unfortunately, most engineering teams do not regularly test the performance and scalability of their infrastructure.
Software development and deployment contexts have changed considerably over the last decade with Agile approaches. Performance testing has had difficulty keeping up with modern testing principles and software development and continuous deployment processes.
Big Data is a big topic in software development today. When it comes to practice, software testers may not yet fully understand what is exactly Big Data. A tester knows that you need a plan for testing it. Since most Big Data lacks a traditional structure, how does Big Data quality look like? And what the are most appropriate software testing tools? This article tries to answer these questions.
James Waldrop of Twitter discusses the tools, process and philosophy that goes into performance testing at Twitter. Particular emphasis will be placed on the Iago open source load testing library, which he wrote to enable Twitter’s engineering teams to perform load tests before deploying code to production. This presentation dives into implementation details of some of these tests (including source code) and how complicating factors such as OAuth and arbitrary Thrift protocols are managed. Video producer: https://developers.google.com/google-test-automation-conference/ Slides: http://goo.gl/9VY2b
Copyright © 2009-2023 Software Testing Magazine by Martinig & Associates