Test module list view

A test module list view displays a list of all test module contained within either the Tests node or one of its subfolders.

On the TestArchitect explorer tree, when you double-click the Tests node, and then select the Test Modules tab. TestArchitect displays a list view of test modules for the project.
Note: Test module list views are also available for subfolders of the Tests node.

The following operations can be performed on a test module list view:

Common operations

You can find various common operations that can be performed on test module list views here.

Opening a test module

From a list view, you can open a test module in the editor by right-clicking its list view entry, then clicking Open.
Tip: You can also open multiple test modules by using your keyboard's Shift key to select a contiguous range of test modules (or Control to select multiple noncontiguous test modules); then right-click the selection, and click Open.

Creating test suites

Test suites are used to organize and execute test modules based on certain criteria. They provide flexibility in managing execution plans. For example, you can create a test suite based on an existing set of test modules and then execute all of the test modules as a set with a single action. (Learn more.)

Test execution

You can select one or multiple test modules from the list for execution. (Use your keyboard's Shift key to select a contiguous range of listed test modules, or Control to select multiple noncontiguous test modules.) After creating your selection, right-click and select Execute. The Execute Test dialog box then appears, offering you the normal options of selecting test cases, executing tests remotely, etc.

Test results

  • Opening latest test result: If you run a test multiple times, you can conveniently open the most recent test result. (Learn more.)
  • Opening baseline result: If your test module currently has a baseline test result associated with it, you can easily access it. (Learn more.)

Revision control

  • Check-out is the process of creating a local working copy from the repository. When a project item is checked out, a lock is placed on that item preventing other users from modifying it. (Learn more.)
  • Check-in is the process of writing the changes made to a local working copy back to the repository. Checking in a project item releases the lock on it, allowing other authorized users to check out the item and modify it as needed. (Learn more.)
  • Undoing a checkout allows you to cancel a checkout and discard any changes you have made to the local copy. (Learn more.)

Revision history

Repository saves pertinent information on a project item at every check-in. This includes timestamp, assigned version, project name, item type, item name, user who checked in the item, and included comments. (Learn more.)

Project item comparisons

TestArchitect's Diff Tool can be invoked from the listview, allowing you to compare the differences between two project items in the list, or two revisions of the same item.

Cut-Copy-Paste operations, and Delete command

  • From a test module list view, you can remove a given test module from one test folder and paste it to another by performing a cut-and-paste operation from the context menu.
  • The copy-and-paste operation from the context menu allows you to create a duplicate of a selected test module.
    • In addition to the conventional cut-and-paste and copy-and-paste from the context menu, you can drag and drop a project item, or a selection of items, from a list view into a folder or node of the same type in the TestArchitect explorer tree.
    • Performing drag-and-drop within the same project is equivalent to cutting and pasting. Performing a drag-and-drop across different projects, on the other hand, is a copy-and-paste operation.
    • During a drag operation, at any time your mouse pointer is over a location that cannot accept the type of item being dragged, the pointer turns into a black crossed circle . Releasing the mouse button at this point simply cancels the operation.
  • Use the Delete command from the context menu to remove the selected test module(s).

Name change propagation

The process of renaming a given entity so that the change propagates to all references to that item is known as name change propagation. Renaming an entity automatically updates all applicable action lines, test modules, and action definitions where the entity name appears. (Learn more.)

Exporting test module to external files

Test modules can be exported to .ZIP or .CSV files, which can be used as a backup or for re-importing.

Importing test cases from CSV files

Test cases can be imported from .CSV files into a test module.


TestArchitect can generate reports to show the progress of the test or automation development, as well as test run performance and results. (Learn more.)

Integration with third-party tools

TestArchitect seamlessly integrates with several powerful third-party tools, to assist in application development, continuous integration, and test management. Interfaces with HP Quality Center (QC), Team Foundation Server/Microsoft Test Manager (TFS-MTM), and Zephyr are all available to extend TestArchitect's functionality and empower your and your team.

  • HP Quality Center:
    • Importing QC tests into a TA test module (learn more)
    • Uploading TA test modules/test cases to QC (learn more)
    • Mapping TA test cases to QC tests (learn more)
  • Team Foundation Server-Microsoft Test Manager:
    • Import TFS test cases to TA (learn more)
    • Uploading TA test modules/test cases to TFS (learn more)
    • Mapping TA test cases to TFS test cases (learn more)
  • Zephyr:
    • Importing Zephyr test cases into TA (learn more)
    • Uploading TA test modules/test cases to Zephyr (learn more)
    • Mapping TA test cases to Zephyr test cases (learn more)


You can automatically replace a word or phrase with another in a field of a test module list view - for example, you can replace Log in with Sign in as the name of a test module.

The contents of fields in test modules can be replaced if they are editable fields. Note that this includes the Name field (that is, the name of the test module), and that, when the Replace function is used to change a test module name, name change propagation is applied (see Name change propagation).
  1. Open the test module list view. For example: Double-click the Tests node on the TestArchitect explorer tree. The test module list view appears in the main panel.
  2. On the test module list view, right-click a test module, and then click Replace. The Replace dialog box appears.

  3. In the Find What box, type the text that you want to search for.
  4. In the Replace With box, type the replacement text.
  5. Do one of the following:
    1. To replace an occurrence of the text, click Replace. TestArchitect searches the editable fields of each test module listed for the item to be replaced. The search path is cell-by-cell beginning from left to right and down row-by-row starting from the active cell until a match is found. TestArchitect replaces the first matched item (if that item is in an editable field), performs name change propagation where applicable (that is, on test module names), and sets the active focus to the replaced cell.
    2. To replace all occurrences of the text, click Replace All. TestArchitect replaces all occurrences of the item (wherever they belong to editable fields) and performs name change propagation where applicable.


You can directly edit the value of a field in a test module list view.

Editable fields fields of test modules listed in test module list views can be edited directly. Where applicable (that is, in the case of modifying a test module's Name field) the change is propagated to all references to the changed item, in a process called name change propagation (see Name change propagation).
  1. Open the test module list view. For example: On the TestArchitect explorer tree, double-click the Tests node. The test module list view appears in the main panel.
  2. Select a test module in the test module list view. For example, Calculation.
  3. Double-click an editable field of the selected test module (for example, the Name field), or press F2 on the keyboard. The selected field becomes the active cell, and editable.
  4. Enter the new data.
    Tip: For multi-line fields, such as Notes, Description, etc., press Alt + Enter to insert new lines within the cell.
  5. Press the Enter key to complete the change.
The field is edited and updated. If it is a Name field, name change propagation replaces all references to it with the new name.

Editing test module variations

You can re-link a test module variation to other version nodes or keywords via the Edit Variations dialog box.

Ensure that the test module variation that you want to re-link to other version nodes or keywords is checked-out.
  1. Open the test module list view. For example: On the TestArchitect explorer tree, double-click the Tests node. The test module list view appears in the main panel.
  2. Select a test module variation that you want to re-link to another version node or keywords.
  3. From the context menu, select Edit Variation. The Edit Variation dialog box appears.

  4. Re-link the selected test module variation to other versions or keywords. For more information, see Creating keyword variations and Creating a variation.
  5. Click OK.
The selected test module variation is re-linked to other version nodes/keywords.