Before starting with the hands-on tutorials, let’s review some of the basic features and ideas behind TestArchitect and the Action-Based Testing model.
TestArchitect is an integrated development and execution environment for automated software testing. Development efforts in TestArchitect are organized into projects, and projects are stored in repositories, which may be shared by other users on a network. The more basic assets of a project, known as project items, include test modules, actions, data sets, interfaces, and test results. A revision control system built into TestArchitect protects against the danger of different users modifying the same project item concurrently, and ensures that older revisions of all items are archived and accessible.
Tests in TestArchitect are grouped into test modules, each of which can consist of any number of test cases. Each test case is written as a sequence of action lines, with each action line calling a specific action and, in most cases, supplying it with arguments. The actions called may be ones that are built into TestArchitect (built-in actions), or written by you or your team (user-defined and user-scripted actions).
Test modules, user-defined actions, and other TestArchitect project items are developed and maintained in the TestArchitect editor, a multi-featured tool that uses a familiar worksheet interface.
TestArchitect relies on repositories to store test assets.
Actions, which are at the heart of the Action Based Testing™ methodology, form the building blocks of TestArchitect tests.
The test module and template
By default, test modules present a template that assists you in creating well-formed tests, ones that conform to the Action Based Testing methodology.
Test editor basics
The TestArchitect test editor is used to create and modify action-based tests.