What skills are required to run a realistic test campaign?
You have probably read countless articles about what a good tester is. Of course this is a tricky question and there is no perfect answer. Performance testing requires a mix of technical, organisational and communication skills.
I have seen good technical testers fail to deliver the right message even if they identified the source of all issues.
On the other hand, I have seen performance testers with low technical skills perform very well thanks to their communication.
Thoughts and good practices about how to present performance tests results in an efficient way.
Since I started my career as a tester, I’m often impressed by how disregarded communication in load and performance testing is. However, you can be as skilled as you want as a technical tester, if you can’t explain your analysis and convince decision makers to take actions, most of your work was in vain. In fact, I’ve seen colleagues who were not interested in the technical aspects of the job get better customer satisfaction.
How do I select the right environment for my load tests? Testing early and testing in production.
We can all agree that running a realistic load test is important to assess server performance correctly. One of the aspects of such a test is the testing environment. It must be selected carefully based on your requirements.
The sooner the better Since I began my career as a tester I’ve been told it is better to test early to prevent costly defects. But sadly I must admit I ran a lot more tests in production than in an early Q&A environment.
As testing evolves, is the test plan mandatory in every situation?
Should I do a test plan? If you are a tester, chances are you already know what a test plan is. If not, the short definition would be : “A specification document of your load test campaign".
This document is very close to the functional test plan in its structure because both share some common ground. The question I’m often asking myself when preparing a load test is if this document should be used at all.
Couchbase is a popular NoSQL Database. I’m working with this database for about a year. I like this database for several reasons:
Easy to install: a single .deb file to dpkg on Ubuntu, Fast: it serves queries within milliseconds, Distributed: you can build a distributed cluster with tens of machines. The biggest downside with this database is that it consumes almost 20% of cpu on our m3.large AWS instance for no reason.
Thoughts on how to define simple yet accurate virtual user profiles.
One of the questions I hear the most from newcomers preparing load tests is about defining proper virtual user profiles.
If you are familiar with testing, you probably heard about the 80/20 rule, also know as the Pareto principle. Apart from impressing the ladies at parties (you know, probably), this principle states that roughly 80% of the effect (performance) comes from 20% of the cause (functionalities in our case). This principle is widely used when selecting the functionalities to test and avoid too much and/or too long user profiles.
Why load testing an e-shop is not a walk in the park. Our advices to deal with it.
As a performance tester, I am always surprised to see how unprepared most retail websites are. Even when load testing has been done (to prepare for sales or marketing campaigns), most of the time it is nowhere close to the real users behavior. We’ve already seen the importance of response times in a previous article, but there are other aspects we should consider.
For instance, unless you spent the past years on a different planet, you have probably seen these videos where thousands of people rush into stores during sales.
This post is a step by step guide to create a CRUD REST Endpoint using Node.js, Express and TypeScript.
The Goal I want to setup a simple REST server that allows to Create, Read, Update and Delete data (Users in this case) using Node.js, Express, and TypeScript:
Quick AngularJs tutorial on how to create and test a ‘domain name’ filter.
The Domain Filter Problem Until now, we used default names such as ‘Untitled VU’ for virtual users created in octoperf, our load testing tool. That’s not very relevant. So we changed it to the domain name of the tested website.
The load tester selects a URL to test, and we need to extract the domain name from it.
The Hyperlink Solution A nice trick is to create an hyperlink element <a href=".
A quick test of TypeScript using WebStorm and Node.js
We use AngularJs at OctoPerf.com, for the frontend of our load testing tool. As AngularJs V2 quick start guide uses TypeScript, I think it’s a good motivation to give it a try.
Prerequisite Node.js and npm must be installed to run this sample. WebStorm is used to automatically transpile our .ts files (compile them to .js ones).
We can also use the command line transpiler:
npm install -g typescript to install it.