Language menu for mobile

Action Based Testing

The Action-Based Testing™ method represents the continued evolution of the keyword-based testing approach and is the foundation of LogiGear's Test Automation toolset, TestArchitect™, which uses keywords to create and automate the majority of tests without scripting of any kind.

Action-Based Testing™ (ABT) provides a powerful framework for organizing test design, Automation and execution around keywords. In ABT, keywords are called actions to make the concept absolutely clear. Actions are the tasks that are executed during a test. Rather than automating an entire test as one long script, tests are assembled using individual actions. Non-technical Test Engineers and Business Analysts can then define their tests as a series of these automated actions.

Unlike traditional test design, which begins with a written narrative that must be interpreted by each Tester or Automation Engineer, ABT test design takes place in a spreadsheet format called a test module. Actions, test data, and any necessary GUI interface information are stored separately and referenced by the main test module.



by Mark Fewster and Dorothy Graham

This book describes how to build and implement an Automated Testing regime for software development.
by Hans Buwalda, Dennis Janssen, Iris Pinkster and Paul Watters

Zero-defect software is the holy grail of all development projects, and sophisticated techniques have emerged for automating the testing process so that high-quality software can be delivered on time and on budget.



TestArchitect for Visual Studio is a keyword authoring platform extension designed specifically to enhance coded UI Test Automation in Visual Studio 2012.
There is no single recipe to make big testing a big success. It takes planning and careful execution of the various aspects, like test design, infrastructure and organization – a mix that can be different for each situation in which you may find yourself.
To address the challenges and fears of implementing Automation in Agile projects, LogiGear CTO Hans Buwalda presents Action-Based Testing as the answer.
Agile methods are becoming more and more popular and successful for developing IT systems. Typical properties of an Agile method, like Extreme Programming, are continuous user involvement and an emphasis on the testing role (‘Users’ may be the actual users of the system you are creating, customers, or business analysts who provide the requirements on behalf of the end-users).
Keyword-based testing is gaining ground. More and more organizations see this model, in which tests are not scripted but written as a series of keywords with arguments, as a valuable alternative to record and playback, or scripting of tests. A good theoretical basis for keywords can be found in the well-known Automation book Software Test Automation, by Dorothy Graham and Mark Fewster, and also in numerous articles and white papers on the LogiGear website.
Keyword-driven methodologies like Action-Based Testing (ABT) are usually considered to be an Automation technique. They are commonly positioned as an advanced and practical alternative to other techniques like to “record & playback” or “scripting.”
 Key Success Factors for Keyword Driven Testing
Keyword-driven testing is a Software Testing technique that separates much of the programming work of Test Automation from the actual test design. This allows tests to be developed earlier and makes the tests easier to maintain.
Misconceptions About Test Automation
Test Automation is significant and growing, and yet I have read many forum comments and blog posts about Test Automation not delivering as expected. It’s true that Test Automation can improve reliability while minimizing variability in the results, speed up the process, increase test coverage, and ultimately provide greater confidence in the quality of the software being tested, but in (too) many cases the benefits never
Leveraging Global Talent for Effective Test Agility
Over the years, many Agile proponents have come out strongly against offshoring some of the development team, and in particular against having a remote testing team. We made use of not one, but two separate outsourcing providers located in two offshore locations.

Contact us today to find out how affordable our services are

Talk to an Expert