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.
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 here.
From a list view, you can open a test module in the editor by right-clicking its list view entry, then click Open.
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.)
Option #1: Running tests through the context menu
From the test module list view, you can select one or multiple test modules for test 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.
Option #2: Performing a drag and dropNote:Applies to TestArchitect 8.3 Update 4 and higher.
Invoke the Execute Test dialog. In the test module list view, select additional preferred test modules. Next, drag these test modules from the test module list view to the desired position in the Test Modules panel of the Execute Test dialog box.Important:Only test modules which belong to a single project are allowed.
- 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.)
- 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.)
TestArchitect’s Diff Tool can be invoked from the list view, allowing you to compare the differences between two project items in the list, or two revisions of the same item.
- For comparing two project items, see Comparing project items with Diff Tool.
- For comparing two revisions of a project item, see Comparing a project item’s revisions with Diff Tool.
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.Tip:
- 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).
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.)
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.)
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), and Team Foundation Server/Microsoft Test Manager (TFS-MTM) are all available to extend TestArchitect’s functionality and empower your and your team.
- HP Quality Center:
- Team Foundation Server-Microsoft Test Manager:
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.
You can directly edit the value of a field in a test module list view.
Editing test module variations
You can re-link a test module variation to other version nodes or keywords via the Edit Variations dialog box.