TestArchitect Release Notes

TestArchitect 8.1 Update 3 Release Notes

Release Date: April 27, 2015

What's New in TestArchitect 8.1 Update 3

The following new features and improvements are introduced in the latest version of TestArchitect running under Windows.

TestArchitect Automation

New features

1. Web automation on Google Chrome now utilizes Google’s Remote Debugging technical approach. Google is phasing out support for NPAPI, the technology previously employed by TestArchitect to automate web applications on Chrome.
2. All HTML input types are fully supported on web browsers including Internet
   Explorer, Mozilla Firefox, and Google Chrome.
   • New input types of the <input> element are supported as unique TA classes:
     • <input-color>
     • <input-date>
     • <input-datetime>
     • <input-datetime-local>
     • <input-email>
     • <input-month>
     • <input-number>
     • <input-range>
     • <input-search>
     • <input-tel>
     • <input-time>
     • <input-url>
     • <input-week>

Enhancements to existing features

1. Each HTML <input> type control is now mapped directly into a unique TA class. (Note: In earlier versions of TestArchitect, this only applied to pre-HTML5 <input> type controls: that is, <input-button>, <input-password>, <input-text>, <input-submit>, <input-checkbox> and <input-radio> were mapped to distinct TA classes; all others were mapped into the general input-text TA class.)
2. If you captured the newer <input> type controls in a previous version of TestArchitect, your TA class mappings of those controls are no longer recognized by the current version in its default mode.
   You have two options:
   • Recommended: Recapture the controls so that they are mapped into their appropriate TA classes. (For example, remapping an <input-color> control will change its TA class mapping from the legacy input-text class to the new input-color class.)
   • Leave your legacy mappings intact and set the ignore html input types built-in setting to yes in all tests that interface with HTML <input> type controls.
     Note: ignore html input types built-in setting: Determines whether, during the test execution, the TA classes of legacy-captured HTML <input> type controls are taken into consideration.
3. enter built-in action is now applicable to these additional HTML <input> type controls:
   • <input-datetime>
   • <input-email>
   • <input-number>
   • <input-search>
   • <input-tel>
   • <input-url>
4. set built-in action is now applicable to these additional HTML <input> type controls.
   • All <input> type controls supported by enter built-in action
   • plus:
     • <input-color>
     • <input-date>
     • <input-datetime-local>
     • <input-month>
     • <input-range>
     • <input-time>
     • <input-week>

Known Issues

• Testing web automation on Google Chrome:
  • Automation is unable to work if the Interface Viewer is open.
  • Minimizing the target Chrome window renders the Interface Viewer and the Identify feature unable to locate web controls, and automation playback fails.

System Requirements

The following table lists the recommended hardware and software requirements for TestArchitect.

Recommended system requirements

Additional Resources

• For more information, please visit our website at www.testarchitect.com or email us at [email protected].
• On a system with TestArchitect installed, help is available at:
  Start menu > All Programs > TestArchitect > TestArchitect Help.