Courses

Building The Test Automation Framework

What You’ll Learn

Amazon Web Services: the platform we’ll use for building out our windows and unix test automation environment.
Jenkins: the continuous integration tool we’ll use to build the application under test and trigger all our automated test actions.
Selenium: the test automation tool we’ll use to run our GUI browser based automation tests.
SoapUI: the test automation tool we’ll use to run our API based automation tests.
Git: the source code tool we’ll be managing and retrieving the source for our application from.
JMeter: the load test tool we’ll use to asses the performance of the application under test.

Course overview

Building The Test Automation Framework

Introduction

Welcome to Building the Test Automation Framework. A 6 part course that takes you step by step through the process of building a test automation framework. A test automation framework we’ll build completely from open source tools. Each of the 6 modules is a short course in it’s own right. Each module covering tools like; Amazon Web Services, Jenkins, Selenium, Git, SoapUI and JMeter.

Module 1: Part 11: Jenkins Post Build Actions and Smoke Tests
Module 2: Part 10: Setting Jenkins up to install the AUT
Module 3: Part 9: Jenkins Slave Machine
Module 4: Part 8:Instance Initialisation Script
Module 5: Amazon Web Services Conclusion
Module 6: Part 11: How to Check Your AWS Spend
Module 7: Part 10: The Difference Between AWS Terminate and AWS Stop
Module 8: Part 9: Connecting to the Unix Client Machine
Module 9: Part 8: Installing Putty and SSH on the Windows Machine
Module 10: Part 7: Connecting to the Windows Master Machine
Module 11: Part 6: Running up the Ubuntu Unix Instance (VM)
Module 12: Part 5: Running up the Windows Instance (VM)
Module 13: Part 7: Starting the Linux Amazon Instance Slave
Module 14: Part 6: Amazon AWS Integration
Module 15: Part 5: Configuring Jenkins
Module 16: Part 4: Installing Plugins
Module 17: Part 3: Jenkins’ Plugins
Module 18: Part 2: Jenkins Configuration
Module 19: Why use Jenkins
Module 20: Part 4: Creating a Security Key Pair
Module 21: Part 3: Configuring Security Groups
Module 22: Jenkins Prerequisites
Module 23: Part 1: Installing Jenkins

Jenkins

We have the test environment in place and we know enough to be dangerous with Amazon Web Services. Next step is probably the most important. We need to get Jenkins installed, configured and running. Jenkins has to be one the testers most useful tools. It’s not just handy for kicking off automated tests it’s indispensable for automating all sorts of processes you have to complete day in day out.

Module 24: An Introduction to Jenkins
Module 25: Part 2: AWS Fundamentals
Module 26: Part 1: Creating an AWS Account
Module 27: What will your finished setup look like?
Module 28: Amazon Web Services Prerequisites
Module 29: Why Use Amazon Web Services

Amazon Web Services

Our 6 module course on Building the Test Automation Framework starts with Amazon Web Services (AWS). We’re going to use AWS, and more specifically, the Elastic Compute Cloud (EC2) to build our test environment and automation system. It all starts with configuring and running up the virtual machines we need to run everything on.

Module 30: An Introduction to Amazon Web Services
Module 31: Introduction to Building the Test Automation Framework
Module 32: Part 12: Starting Subsequent Jenkins Builds
Module 33: Jenkins Conclusion

Selenium Browser Automation

We’re going to configure our system so that we automatically start a Windows test machine that we’ll run a set of Selenium browser tests from. This client windows machine will be automatically started by Jenkins. Once running the Selenium scripts will be started by another Jenkins project.

Module 34: The Tools We’ve Chosen
Module 35: Prerequisites Selenium Browser Automation
Module 36: Part 1: Setup Our Windows Test Machine
Module 37: Part 2: Configuring Jenkins to Start A Windows Slave Machine
Module 38: Part 3: Completing the Windows Client Configuration
Module 39: Part 4: What to do when you Can’t Connect the Windows Slave
Module 40: Part 5: Installing the Software we need on the Windows Slave
Module 41: Part 6: Create Our First Selenium Script
Module 42: Part 7: Running the Selenium Script from the Jenkins Master Machine
Module 43: Part 8: Checking we can Access Rocket Chat from our Windows Client
Module 44: Part 9: Writing Some Selenium Tests for Rocket Chat
Module 45: Part 10: Running an RDP/RDC Session on our Master Jenkins Machine
Module 46: Part 11: Closing the RDP/RDC Session on our Master Jenkins Machine
Module 47: Part 12: Running the AUT build followed by the Selenium Tests
Module 48: Selenium Browser Automation Conclusion
Module 49: Prerequisites
Module 50: The Tools We’ve Chosen
Module 51: Part 1: Install SoapUI
Module 52: Part 2: Connect to the Rocket Chat API
Module 53: Part 3: Creating Some REST Requests
Module 54: Part 4: Converting the REST Requests to Tests
Module 55: Part 5: Running the SoapUI Test Suite from the Command Line
Module 56: Part 6: Running the SoapUI Test Suite from Jenkins
Module 57: Part 7: Reporting the SoapUI Test Results in Jenkins
Module 58: Conclusion
Module 59: The SCM Tool We’ve Chosen

JMeter

In this Moudule we’re focusing on running our performance and load tests. We’ll create some simple scripts in JMeter and link the execution of these scripts into our build process with Jenkins. Once our Selenium functional tests and our SoapUI REST API tests are complete we’ll kick off these JMeter tests.

Module 60: Running Our Performance Tests with JMeter
Module 61: Prerequisites
Module 62: Part 1: Install JMeter
Module 63: Part 2: Initial Configuration of JMeter
Module 64: Part 3: Configuring Our Performance Tests
Module 65: Part 4: Configuring our Linux Performance Test Server
Module 66: Part 5: Parameterise our JMeter Project
Module 67: Part 6: Add and configure the Jenkins Performance Plugin
Module 68: Part 7: Configure the Jenkins Job to Deploy our Performance Tests
Module 69: Part 8: Check the Performance Job and Configure in the Whole Build Chain
Module 70: Conclusion

Source Code Control

In this final module we’re looking how we can best control all of our test resources and files. We’ve created Selenium, SoapUI and JMeter tests. The files for all of these tests are now scattered all over our distributed test automation environment. Not great for colloaboration, maintaining versions and backups. Down right dangerous really.

Module 71: Overview
Module 72: What You’ll Learn

Executing Our REST API Tests

In this Module we start to put together some API tests to check the REST Api that is delivered as part of a Rocket Chat install. The moment the Selenium tests complete Jenkins will trigger SoapUI to run a number of REST based API tests from the one of the Windows AWS client machines.

Module 73: The Tools We’ve Chosen
Module 74: Prerequisites
Module 75: Part 1: Sart a Unix Ubuntu Git SCM Server
Module 76: Part 2: Setup the Security Group and SSH Connection
Module 77: Part 3: Install Git
Module 78: Part 4: Configure the Git User Account
Module 79: Part 5: Configure the Git Server
Module 80: Part 6: Commit Our Selenium Source Code to the Git Server
Module 81: Part 7: Commit our Selenium Script to our Git Repository
Module 82: Part 8: Updating our Jenkins Job to Use the Git Repository
Module 83: Part 9: Modify and Commit our Selenium Scripts from another server
Module 84: Conclusion

Building The Test Automation Framework

What You’ll Learn

Course overview

Building The Test Automation Framework

Introduction

Jenkins

Amazon Web Services

Selenium Browser Automation

JMeter

Source Code Control

Executing Our REST API Tests

Company Info

Training

Test Management Tools

Contact Us