Classifying UI-interactive actions

Timing settings used for a given action are largely determined by the type of action it is. Actions that interact with the AUT can be classified into UI-testing and UI-interfacing actions. Each group can be further classified into subgroups.

In TestArchitect, there are several types of actions which test the user interface in some way. Additionally, another set of actions interact with the AUT in a non-testing manner, such as clicking a button. All these actions use one or more timing settings. Let’s examine how we might categorize these actions.

For purposes of this topic, we only consider TestArchitect actions that relate to the user interface of the AUT, as they are almost the only ones that involve timing settings1. These make up the majority of built-in actions, and can be grouped into two sets, with each set further divisible into subgroups:


1One exception to this rule is get clipboard, which does not interact with the AUT, but does use a timing setting.

2Note that, when we refer to these actions, we’re including the not exists actions as well.

Copyright © 2023 LogiGear Corporation. All rights reserved. LogiGear is a registered trademark, and Action Based Testing and TestArchitect are trademarks of LogiGear Corporation. All other trademarks contained herein are the property of their respective owners.

LogiGear Corporation

1730 S. Amphlett Blvd. Suite 200, San Mateo, CA 94402

Tel: +1(800) 322-0333