The following new features and improvements are introduced in TestArchitect version 8.2
running under Windows.
- Before upgrading to the latest version of TestArchitect,
it is strongly recommended that you back up all repositories.
- A TestArchitect client and any repository server to which
it connects must be of the same version.
execution: Time-traveling execution provides support for retroactive execution,
that is, the ability to execute a particular historical snapshot, or set of revisions, of
project items in a given project. Given its ability to find the right set of test assets
for a particular past version of an application, time-traveling execution is well-suited
for regression testing on AUT versions that precede the current release.
- Implementation of time-traveling execution has necessitated structural changes to
TestArchitect repository databases. An upgrade tool is provided to allow you to take advantage of time traveling
on repositories created prior to TestArchitect version 8.2.
- Note that repository databases belonging to TestArchitect version 6.4 or earlier
must be upgraded in stages:
- If your TestArchitect version is 6.4 or earlier, upgrade TestArchitect to any
version between 7.3 and 8.1.
- From a TestArchitect 7.3-8.1 installation, run the repository upgrade tool.
This upgrades your repository databases to support name change propagation
(learn more), a prerequisite for time
- Upgrade to TestArchitect version 8.2.
- Run the 8.2 repository upgrade
tool. This upgrade provides time traveling support to your
- Support for time zones: To help teams spread across different
time zones, TestArchitect can now automatically display
date and time values for project assets relative to the time zone in which they are being
viewed. As an example, during the months of Daylight Savings Time, Vietnam is 14 hours
ahead of the U.S. Pacific Time Zone. Hence, if a team in California checks in a project
item at 3:00pm on January 1, Vietnamese engineers see the item as having a Last
update date of 5:00am, January 2.
Enhancements to existing features
- Support for
creating a branch in variations: Branches are most typically used to
represent the test changes implemented to accommodate series of patches or hot fixes,
usually involving such things as bug fixes or performance enhancements for a given
version of an AUT. Note that you may also create subtrees of version nodes under branch
- Support for picture checks
in project subscription: Picture checks stored within the
Picture Checks node can now be shared across multiple projects
via subscription. In other words, your project can reuse picture checks that reside in
- Enhanced support for Revision
Control: TestArchitect Revision Control saves pertinent information on a
project item every time it is checked in. Each revision is now identified by the
- timestamp (that is, the checked-in date and time)
- assigned AUT versions
- host project name
- project item type
- project item name
- user who checked in the item
- check-in comment
- New UI for the Version
History dialog box.
- Support for Context-sensitive
built-in settings: Positioning your
cell pointer over a built-in setting in the test editor and pressing
F1 opens TestArchitect Help with
the associated reference topic displayed.
- Team Foundation Server-Microsoft Test Manager integration
- Mapping test result
status: Statuses of TestArchitect test results, such as Passed with
Warning/Error, Pending Picture Check(s), and others, can be mapped to corresponding
statuses of Team Foundation Server test results, such as Passed, Failed, or
- Mapping a TestArchitect project to a Team
Foundation Server project: Mapping a Test Architect project to a Team
Foundation Server team project allows you to upload test results to TFS.
- Importing Team Foundation Server test
suites/test cases to
TestArchitect: Test cases or test suites residing on Team Foundation Server
may be imported into TestArchitect, establishing one-to-one mappings between the two
sets of test cases.
- Uploading TestArchitect test modules/test
cases to Team Foundation Server: TestArchitect test cases and test
modules can be uploaded to the Team Foundation Server, which also establishes
one-to-one mappings between the two sets of test cases.
- Uploading TestArchitect test results to Team Foundation Server: Results of
tests executed and stored in TestArchitect from projects mapped to Team Foundation
Server may be conveniently uploaded to Team Foundation Server either manually (via the context menu), or
automatically upon conclusion of a
- Matching custom fields between TestArchitect
and Team Foundation Server: Custom fields in Team Foundation Server
may be mapped to user-defined fields in TestArchitect test modules or test cases,
and vice versa. Mapping is driven by field names. Fields in Team Foundation Server
and TestArchitect are mapped automatically when their names are identical and their
data types are compatible.
- Upgrading build assemblies of the
TestArchitect plug-in: When installed, information for the
TestArchitect-Microsoft Test Manager plug-in is stored in build assembly files.
These files may now be upgraded when necessary - either manually or automatically -
to ease the process of upgrading to a newer version of the plug-in.
- Switching to a different TFS
account: You have the option of rapidly switching from the current
TFS account to a different account.
- INITIAL and FINAL sections are both invoked for each test case
run: When running an automated test, the execution of every single Team
Foundation Server test case entails the execution of both the INITIAL and FINAL
sections of the associated TestArchitect test module, if any. For example, the
execution of test case #01 is preceded by the execution of the INITIAL section, and
followed by the FINAL section; the same is true for test case #02, and each
subsequent test case.
Enhancements to existing features
- Improved Action Recorder for web
apps on Internet Explorer:
- Improved design: Action Recorder now generates test procedures with high stability
and reusability, consistent with Action-Based Testing.
- tabs and newlines can now be generated for the
enter/set action and the Check function.
(The Check function is available on the Recording toolbar and is used to insert checkpoints
into the current test.)
- The XPath TA property is used to identify window and control
definitions that are generated during the recording session.
- Manual keyboard entry of the characters ^, +, % and # is now recorded correctly,
ensuring that they are not misinterpreted as special characters during
- Support for recording tests on Internet Explorer 64-bit version.
- Support in TestArchitect 64-bit for recording
within both the 32- and 64-bit versions of Internet Explorer. (Note, however, that
TestArchitect 32-bit does support recording
within Internet Explorer 64-bit.)
- New built-in actions, navigate and move mouse, are generated during the recording
- In the generated interface entity, reduced the number of TA property-value pairs
used to identify the associated web page: only the doc title
property is now used.
- Action Recorder performance much improved, including start up time and speed of
test procedure generation.