Get Started

This page helps get you started, and provides you with progressively more
advanced information on the many features of TestArchitect

Have you downloaded TestArchitect?

If you have not downloaded TestArchitect, please follow this link for details.
After installing TestArchitect, don’t forget to contact us for your license key.

TUTORIAL - FIRST STEP

See the diagram below to understand the basics of TestArchitect's project items, the concept of interface mapping (in which user interface objects are identified by their properties), and a quick reference sheet related to Action-Based Testing language.
TestArchitect Project Diagram

TUTORIAL - SECOND STEP

Watch this instructional video to learn the Action Recorder, a tool which records your manual operations on the AUT, captures the resulting screen output, generates keyword action lines, and writes the action lines to your test.

Action Recorder: Generate tests automatically by allowing TestArchitect to monitor your manual interactions with the AUT and record them as action lines.

GETTING STARTED

#1: Create a project

Create a TestArchitect repository, the database which stores your projects. Following that, create a project to hold your test assets.

#2: Create a test module

Establish a simple test case. Then create a test module to house that test case, and learn the functional sections of a well-structured test module.

#3: Map the user interface

Explore the concept of interface mapping, in which user interface objects are identified by their properties. Then use TestArchitect's Interface Viewer to capture the UI objects you need, assign logical names to those objects, and store your mappings in interface entities.

#4: Author the test

Populate your test module with the action lines needed to automate your test case. And explore how to accelerate test authoring with the editor's Content Assist toolset.

#5: Run the test & review the results

Execute your test, and view the results that TestArchitect reports, including moment-by-moment screenshots of the target application during the test.

#6: Create a user-defined action

With no change in functionality, encapsulate your system-level action lines into a user-defined action, for purposes of reusability, readability, and proper Action-Based Testing design. Parameterize your new action to maximize its reusability.

Got a problem? We are here to help!

CONTACT SUPPORT

Contact our support team to find the available support options for your TestArchitect products.

KNOWLEDGE BASE

Searchable database of case studies and technical articles.

FORUMS

Find answers to your questions and participate in product feature requests.

TESTARCHITECT HELP SYSTEM

Find your TestArchitect Help system for quick and easy reference.

Discover how organizations
like yours are using TestArchitect
Halliburton successfully utilizes TestArchitect and the LogiGear team in Agile environment to reduce defects by 97%
Centrify leverages the TestArchitect platform to achieve an 80% automation rate
McAfee increases test coverage to 90% & reduces cycle time with TestArchitect while improving time-to-market for a key product release.