Posts

Load testing with Taurus/jmeter and logging the results to ElasticSearch

Image
Purpose: To provide an easy mechanism for running Jmeter tests using Taurus from a docker container against a particular endpoint and logging the results Required to be installed: Docker Git The setup: Pull the repo: git clone https://gitlab.com/sgriffiths/jmeter-taurus-docker.git && cd jmeter-taurus-docker To Run: docker-compose run dev This will run the simple load test against ' blazemeterdemo.com/reserve.php ' endpoint: Running from the terminal should look like this: Logging - ES and Kibana: For the purposes of the run-through we will use the ELK stack running locally in a docker container From your terminal/cmd: docker pull sebp/elk git clone  https://github.com/spujadas/elk-docker.git && cd elk-docker docker build -t sebp/elk . docker network create --subnet=172.18.0.0/16 elastic-esrally-network docker run --rm --net elastic-esrally-network --ip 172.18.0.5 -p 5601:5601 -p 9200:9200 -p 5044:5044 -it --

Load testing ElasticSearch using ESRally and viewing the results in Kibana

Image
Run EsRally against an existing ElasticSeach index and save the results in Kibana Problem : Need to be able to write json queries and run these against an existing ES cluster Want to be able to view the EsRally results in a local ES instance The test run results to be available in Kibana Required to be installed: Docker Git 1. Get and build the ELK stack to store the test results against. Also defines the network so the docker containers can talk to each other. From your terminal/cmd: docker pull sebp/elk git clone  https://github.com/spujadas/elk-docker.git && cd elk-docker docker build -t sebp/elk . docker network create --subnet=172.18.0.0/16 elastic-esrally-network docker run --rm --net elastic-esrally-network --ip 172.18.0.5 -p 5601:5601 -p 9200:9200 -p 5044:5044 -it --name elk sebp/elk Local Kibana Local ElasticSearch ( Chrome plugin is recommended for viewing ES info) 2. Now we have ES and Kibana running its time to get ES rally sorte

Installing ReadyAPI on a Jenkins EC2 instance using X11

This includes the steps to get ReadyAPI (with licence) running on an AWS EC2 instance and the commands needed to run the Jenkins job  Login via SSH as ec2-user  Install Java x64 to /opt/jdk1.7.0_67/: sudo -s cd /opt wget http://download.oracle.com/otn-pub/java/jdk/7u79-b15/jdk-7u67-linux-x64.tar.gz tar zxvf jdk-7u67-linux-x64.tar.gz rm jdk-7u67-linux-x64.tar.gz Install X11 Virtual Frame Buffer (for running headless tests in Jenkins): sudo yum install xorg-x11-server-Xvfb Ensure X11 forwarding is enabled for SSH server: X11Forwarding yes Prepare the Ready! API install directory: sudo mkdir /data/app/ReadyAPI-1.3.1 sudo chown jenkins:jenkins /data/app/ReadyAPI-1.3.1 Reconnect the server using the user that will be using Ready! API (in this case "jenkins") with X11 forwarding enabled on the client: ssh -X -i ~/.ssh/AmazonKeys.pem jenkins@{jenkins URL} Download the latest version of Ready! API to the server:

Running Postman tests on Jenkins using Newman and AWS (Ubuntu 14.04)

Image
We will be using a hosted Ubuntu server so an AWS account is required After creating an AWS account and accessing the console be sure to change the region from default to create the instance in the closest zone : Select EC2 Select Launch Instance Choose Ubuntu Server (build 14.04 at this current time): Choose the default “ Free Tier eligible ’ instance Leave the defaults and select ‘review and launch’ (I selected auto assign public IP) Edit the Security groups to allow traffic in: Namely port 8080 for jenkins (default port) Port 22 for ssh access The security groups should look something like this: Choose Launch Then Create the Keypair Make sure the correct security group is assigned to that instance: Once up and running select connect to get the terminal commands: Open your terminal or command prompt and locate the .pem file that was saved and

Lets Test 2014 - Sydney, Australia

Image
The day of the conference had arrived. Dan and myself flew down the Monday morning on a flight from Brisbane, we arrived in Sydney on a somewhat ‘crisp’ morning and met up with Dean at the luggage carousels. All three of us made a bee line for the hire car (that Dan had organised, thanks Dan!) and made for our escape from airport and up to the Fairmont resort in the Blue Mountains.  Two hours later we finally made it after some unexpected detours on the way, lets just say I won’t get a job as a navigator anytime soon. We headed in to the resort a made a hasty check in, the rooms weren’t ready so we headed down to the conference where we found the the opening workshops were about to take place as we had arrived too late for the keynote by James Bach. I decided to attend the Oliver Erlewein workshop on “ Hacking Performance ” given this was more in line with my current role. The first couple of hours were spent setting up Jmeter then we broke for lunch, which was buffe