The Test Automation Reference Model

This half-day workshop is designed for those wanting to take their understanding of software test automation to the next level.

The workshop is suitable for people who may already be using some testing tools but are lacking a "big picture" understanding of test automation frameworks.

It also provides a good introduction for those considering using testing tools but not sure where to start.

The workshop introduces participants to a test automation reference model that describes the common components found in all test frameworks.

The reference model is presented as block diagram that identifies the components of a test framework and how they are interconnected.

The workshop is highly interactive.

Under the presenters' guidance, participants use sticky notes to build up the reference model on flip charts.

Using the understanding they have gained, they then identify and compare the components of some real test frameworks.

Participants are encouraged to investigate any test frameworks that they are already using.

Course Features

  • Enhances understanding of automated testing
  • Describes a reference model with multiple applications
  • Reference model based on a survey of multiple testing tools
  • Based on a two-day course Concepts of Automated Software Testing offered by Processworks

Participant Benefits

  • Identify the features, strengths and weaknesses of different testing tools
  • Decipher the terminology vendors use to describe their testing tools
  • Compare different testing tools and identify missing components and features
  • Evaluate and select appropriate testing tools
  • Integrate different categories of testing tool and tools from different vendors
  • Design and implement in-house testing tools, either from the ground up or to enhance and extend open source test tools

Who Should Attend

  • Those who want develop their careers by improving their understanding of automated software testing, such as Test Engineers, Test Analysts, Quality Assurance Staff, Software Developers, Software Engineers and Solution Architects
  • Those who need to plan and manage automated software testing activities, such as Test Managers, Software Development Managers, Product Managers, Product Owners and Engineering Managers
  • Those who who want to gain an understanding of automated software testing, such as Scrum Masters, Business Analysts, Business Systems Analysts, Systems Analysts, Functional Analysts, Systems Engineers, Electrical Engineers, Methodologists and Process Improvement Staff

Course Duration

  • Half-day

Course Agenda

What is a reference model?

Some examples and uses of reference models

Why do we need a test automation reference model?

Guided tour of the reference model components

  • Managing and organising test data
    • Data driven testing
    • Keyword and scriptless testing
  • Determining the expected result of a test case
    • Test oracles
    • A-B testing
  • Managing and launching tests scripts
  • Parsing test data
  • Checking assertions
  • Logging failures
  • Developing test scripts
  • Connecting to the system under test
    • Fixtures
    • Adapters
  • Developing stubs and mock objects
  • Capturing and replaying test scripts

Using the reference model

  • Understanding and comparing testing tools
    • Mapping vendor terminology to the reference model
    • Comparing features
    • Identifying strengths and weaknesses
    • Identify missing components and features
  • Evaluating and selecting testing tools
    • Using components of the reference model as evaluation criteria
    • Adding other evaluation criteria
      • Vendor reputation and market positioning
      • Proprietary vs. open source
      • Cost
        • Acquisition costs
        • Support costs
      • Availability and quality of support
      • Availability and cost of training
      • Platforms supported
      • Programming languages supported
      • Complexity and learning curve
    • Scoring and weighting evaluation criteria
  • Integrating testing tools
    • Different categories of testing tool
    • Tools from different vendors
  • Enhancing and extending open source testing tools
  • Designing and implementing in-house testing tools
    • Using the framework guide the tool architecture
    • Building from the ground up or enhancing and extending open source tools?