The requested page is not available for selected version.
What's new in TestArchitect for Windows
The following new features and improvements are introduced in the latest version of TestArchitect running on Windows.
Remember:
- Before upgrading to the latest version of TestArchitect, it is strongly recommended that you check in all test artifacts and back up all repositories.
New features
- Support mobile testing: Introduced mobile automation testing for native mobile applications and mobile hybrid applications.
TestArchitect Client
- Connect to Device: From Interface Viewer, you can connect to a specific mobile device in the Appium Server with inputting desired capabilities.
- Mobile Live Screen: Witness the magic of the “Mobile Live Screen” feature, where you can literally bring the mobile device screen right in front of your eyes and you can easily capture controls.
- Screenshot recording: captures screenshots during mobile test execution for each UI-interactive action.
- New Mobile actions:
TestArchitect Automation
- Mobile Built-in Actions (ABT): To streamline testing on Native applications for both Android and iOS, we now offer a comprehensive set of business actions for all common controls. From Buttons and Text Views to Labels, Radios, Checkboxes, Listviews, and Comboboxes, we have you covered!
- Testable Android and iOS Hybrid Applications: We’ve expanded TestArchitect’s competencies to cover testing of Hybrid (WebView) applications. You can now employ all the common built-in actions, such as “tap” on elements, “enter” text in “input-*” tags, “get/set” element’s value, and “check control exist,” to ensure complete testing coverage.
- Out-of-the-Box Java Harness Action: While TestArchitect offers a rich set of built-in actions for convenient automation testing, we understand that some users may require custom business logic actions. To support this need, we’ve exposed a set of APIs for Java harness calling, including AbtAutomation, AbtEntity, AbtElement, and AbtDevice classes. Moreover, you can attach to the “current device session id” from Java harness actions, enabling the freedom to use alternative libraries to drive your automation tests.