Action Based Testing

Modular-design, action-based test method

Action Based Testing

Action Based Test Method (ABT)

Test design a significant factor in automation success. Irrespective of the automation technology employed, poorly designed and organized tests will be a continual burden for the automation team. ABT is a method that addresses test design challenge that limits the success of test automation.

  • ABT is a method that enables optimizing test automation production efficiency.
  • ABT makes it possible to achieve test automation critical mass— the point where a positive return on the time and resource investment in test automation is achieved and can be sustained.
  • ABT minimized the effort required to maintain tests.
  • ABT makes it possible to automate 95% of tests using only 5% of the total test effort for automation.
Action Based Test Method

ABT Overview

ABT Overview

ABT is a modular-design and action-driven test method that provides a systematic approach to increase the success of automated testing. Modular-design addresses the challenges of test planning and test case management through efficient test organization.

Action-driven test development eliminates the majority of the programming work required to automate and maintain tests long-term.

ABT consists of three parts:

  • Top-down, modular test planning
  • Test Module development
  • Action-driven test authoring

ABT Components

Modular Test Planning

A top-down panning approach creates a logical test flow that results in more efficient test creation. It also facilitates developing test cases free of unnecessary details and redundant checks that make tests difficult to debug and maintain when the application under test changes.

Test Modules

Test Modules are containers for organizing tests—typically around user stories or software requirements. Test Modules increase the efficiency of test development by providing a well-defined test case flow.

Tests within a module can have interdependencies, but test modules are intended to be independent from one another. This simplifies maintenance and allows different parts of a project to be parsed out to different teams without impact to the overall test project.

Action-driven test authoring

Actions are similar to keywords in that the majority of the programming work of automating tests is separated from the actual test design. TestArchitect’s built-in actions are pre-programmed with dynamic functionality, allowing a single test to run against multiple platforms agnostic.

Actions create a plain text, business-readable, domain specific language to optimize test automation production. This mini-domain specific language is called Action Based Testing Language (ABTL) that follows an activity -> outcome syntax. ABTL

Tests consist of actions specifying activity followed by outcome. This makes it possible for testers to write tests using one or more actions rather than lengthy scripts detailing operations and checks.