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!
JMeter Cloud Blog
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:
E-mail is one of the most commonly used communication channels in the modern world. Gmail, Hotmail and Yahoo Mail have over 1 billion registered users. Over 300 billion email messages are sent daily and 3.5+ million emails are sent every second. Having your “own” email server is the de facto standard for most businesses. And the majority of ECM, CMS and other enterprise solutions have inbound and outbound email integrations - no wonder email server performance is such a hot topic!
In my last post I covered the Challenges of Performance Testing in a Scaled Down Environment. This week, I’m going to address what you should check when scaling down for a performance test.
It’s been an exciting week here at BlazeMeter. In last week’s blog post, our CEO Alon Girmonsky revealed our revolutionary new FollowMe technology – a feature that allows you to run instant performance tests without the scripting, without the software, and without the hassle!
HP LoadRunner Performance testing for websites is something which, in the past, was mostly done with software tools installed on local machines. Take for example HP's LoadRunner, probably the most well known tool in the world of performance testing (it’s been around for a while).
Yep - you read it correctly. In fact, I’d go so far as to say that we’ll soon say goodbye to test scripting, scheduling, and preparation as we previously knew it. Large-Scale Performance Testing - The Old Paradigm How many times have you run a test and found that things aren’t going to plan? You think you’ve thought of everything. You carefully followed a lengthy, expensive and complex set of iterations which included: