Overview | TestArchitect

Action Based Testing Method (ABT)

Test design is a significant factor for automation success. Regardless of the automation technology employed, poorly designed and organized tests will be a continuous burden for the automation team right from the start. Action Based Testing^TM (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 minimizes the effort required to maintain tests.
ABT makes it possible to automate 95% of tests while using only 5% of the total test effort for automation.

Action Based Testing Method for TestArchitect

Download

ABT Overview

ABT is a modular-designed and action-driven test method that provides a systematic approach to incrementally 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 Design Process

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

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 impacting the overall test project.

Actions are keywords in which 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.
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.
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.

Action Based Testing Modernizers Keyword Driven Testing

Action-Based Testing Modernizes Keyword-Driven Testing

Action-Based Testing is a modern approach to Keyword-Driven Testing – the test development method we all know and love. Like everything else, Keyword-Driven Testing evolves. Check out the whitepaper below to understand the most common mistakes in implementing Keyword-Driven Testing solutions and how to avoid them.