Building The Test Automation Framework

Register for this course

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


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.

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.


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.

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.

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.


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.

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.