There are just over 12 weeks left until Black Friday. That’s around 87 days, 2088 hours, or 125,280 minutes that you have left to identify and fix any possible issues that could arise on the big day. Here are some other Black Friday statistics that might interest you: - In 2013, online sales were 15% higher than the previous year - Last year mobile traffic grew by 34% from 2012
JMeter Cloud Blog
Load testing is a vital part of any web-based application testing process. It helps us determine a system’s behavior under both normal and anticipated peak load conditions. It also helps identify the maximum operating capacity of an application, potential bottlenecks and elements that may be contributing to performance degradation.
Is your application, server or service is fast enough? How do you know? Can you be 100% sure that your latest feature hasn’t triggered a performance degradation or memory leak? The only way to be sure is by regularly checking the performance of your web or app. But which tool should you use for this? In this article, I’m going to review the pros and cons of the most popular open source solutions for load and performance testing.
Load Tests Aren’t Just About Threads, Response Times and Hits/s.. If you often run load tests, you probably have a mental checklist of questions that run through your mind, including: - How many threads per JMeter engine should I use? - Can my engine handle 10% more threads? - Should I start with the maximum number of threads, or add as I go?
Load testing without logs is a bit like flying a plane without ever looking at your dashboard By Trevor Parsons, Co-founder and Chief Scientist, Logentries
When it comes to backend and functional testing, API and UI tests pretty much cover all your needs. You run API tests to check your backend functionality and UI tests for your actual user scenarios. Simple right? But do you really know when you should be running an API test and when a UI test is better? Or how to integrate these tests into your application lifecycle? Or which KPIs you should be focusing on? These questions (and more) were covered in this week’s live webinar. Fortunately, we’ve recorded it so you can enjoy it too!
Need to use certificates to provide HTTPS request for your load test? You have two options: 1. Use a server-side client certificate This requires the least amount of work. You use the server to encrypt and decrypt the data. However, occasionally the web application requires a client-side certificate due to security policies.
If you're looking into software testing methods, it’s worth exploring White (or Glass/Transparent) Box testing vs Black Box testing. The idea behind White Box testing is that the tester can observe what happens inside the box during the test. This does involve a level of comprehension in terms of the application's internal architecture and code. Nonetheless, that skill will allow the tester to better understand the ultimate test results.
It still hasn’t been around that long, but Continuous Integration (CI) is already considered a ‘Best Practice’ and is a key element of agile development methodologies. What are Continuous Integration (CI) Processes? If you’re following CI processes, you need to test every change made to your codebase as early as possible. Using tools like Jenkins, TeamCity and Bamboo, developers continuously integrate new or changed code into a shared repository – and verify it with an automated build. Typical CI process steps include: