|Part 1: Getting started with TestArchitect / Introducing TestArchitect|
The TestArchitect test editor is used to create and modify action-based tests.
When you click the Editor subtab of a test module, action definition, interface entity, or data set, you see the worksheet-based TestArchitect test editor. It is here that you create and modify your action-based tests.
The test editor typically looks something like this:
To modify, rather than replace existing cell content, double-click the cell. That puts you into cell-edit mode. Alternatively, if the cell is already selected, you can enter cell-edit mode by hitting the F2 key. Once in cell-edit mode, you may use the Left and Right Arrow keys to navigate through the cell text, or use the mouse to place the text cursor where desired.
When you begin typing an action keyword into column A, TestArchitect uses autocomplete to create a drop-down list of
possible actions whose names match the letters you have typed. Use the
Up and Down arrow keys to navigate through
Press Enter to complete your selection of an action.
Once you have entered or selected an action, the test editor automatically populates the argument names in the row above, as shown in the image below for the enter action.
Sometimes your action lines can be long, expanding past the edge of the editor window.
Functionally, there is nothing wrong with that, but if you want to make your test procedures
more easily readable, you can break an action line into two or more lines with the help of the
line continuation symbol, >>>. The symbol must be placed in column A of
each added line of the action. Be careful to place it at the level of the argument values,
not the headers:
For arguments of actions related to an interface entity or element, when the cell pointer is on a cell and you press Ctrl+Spacebar, a context-based list of available values appears. Select a value using the Up or Down arrow keys and press Enter.
You may have noticed that the first time you pressed the Enter key, the cell pointer moved one cell to the right. After typing into the last argument cell and pressing Enter, the cell pointer repositions itself to column A of the line three rows down. This is part of TestArchitect's intelligent navigation.
With intelligent navigation, TestArchitect anticipates what your next entry will be, and moves the cell pointer to that cell. Most actions take a set number of arguments that are entered into cells immediately to the right of the action's name. The editor, like the automation, is aware of how many arguments a given action takes. As you enter each argument value, pressing Enter causes the editor to move the cell pointer to the next argument cell. Once all the argument fields are filled, the cell pointer moves to a new row (three rows below the current line) in preparation for the entry of a new action line. Additionally, if there are any action lines below the current line (not more than five rows below), pressing Enter moves the cell pointer from the current action line to the next existing action line to facilitate editing.
When content in the editor is changed, a star ( * ) appears next to the item's name in the tab, as shown below in the *Action Based Testing tab. This is an indication that the editor's copy of the file contains unsaved changes.
Ambiguous entities: TestArchitect checks for ambiguous entities (described in Ambiguous entities) before saving the files. If there are ambiguous entities that need mapping, a Select Interface dialog box appears for you to specify which ambiguous entity to map to which interface.
Comments can be used to explain a step in a test, as shown here:
Commenting is also used to temporarily turn off an action line:
The height of rows and the width of columns may be adjusted by dragging the separator line between row and column headers. To resize row height or column width to automatically fit the existing text, double-click the separator line.