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.
From Google Analytics to Discus though Twitter, how can we connect to our visitors.
To follow up on my article about creating blog based on Jekyll, Bootstrap4, Grunt, Bower and hosted on GitHub pages, I’m adding ways of measuring and increasing the number of visitors.
This article is a quick tutorial to do the same, starting from the blog template:
Get to know how many visitors are caught in your blog using Google Analytics, Generate a Sitemap.xml using Jekyll and feed it to Google, Embed Twitter buttons, And use Disqus to handle your articles comments.
OctoPerf last update aims to help our users improve their productivity while load testing their applications.
This short post describes the modifications made to OctoPerf for its last update, and how they can help you save time while load testing.
Our goal is, and has always been, to ease the work of load testers. Creating test reports using Word / Excel can take a lot of time.
Exporting the report That’s why we automated this process in OctoPerf, our load testing solution. Even as your performance bench is running, you can edit the generated report:
A blog’s creation guide, from Jekyll base theme to Boostrap4. Using Grunt/Bower and hosted on GitHub pages.
You can hear him Grunting! The problem I want my blog (the one your’re reading) to be statically and freely served, using my own domain name. I want it to be maintainable and easy to update. And first of all, I really do not have much time for this, so it must be up and running in a few hours.
The solution Bye bye WordPress, Welcome Jekyll. I can handle a couple lines of PHP but it’s not my cup of tea.
Experience feedback on how we use Java 8 for over one year on our servers.
We’ve been using Java8 since the beginning of our startup. Java8 was released on 18 March 2014. We started using Java in September 2014, when AWS made it available on ElasticBeanStalk. At this time, Java 8 was available for almost 6 months. It was mature enough to give it a try.
Frameworks compatible with Java 8 like Spring 4.0 started to be available. Java 8 is a huge step forward compared to Java 7 :
Secure HTTP communication should be the de-facto standard to ensure better privacy.
OctoPerf is fully HTTPS. There is a are several reasons for it. Setting up HTTPS for all our websites (Documentation, Application and Website) is a little bit tedious and pricey1. It took us two days to complete the operation but the result is satisfying for number of reasons.
Why is HTTP so dangerous HTTPS ensures that the communication between our servers and our customers is fully encrypted. Lots of people are using a Wifi connection to go on the internet.