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
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:
You can find various common operations that can be performed on test module list views
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
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.
- 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
- 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.)
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.)
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
- 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
- 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
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
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
- 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
- Importing Zephyr test cases into TA (learn
- Uploading TA test modules/test cases to Zephyr (learn more)
- Mapping TA test cases to Zephyr test cases (learn more)