DeviceAnywhere Enterprise. Release Notes. Release 6.2

Transcription

1 DeviceAnywhere Enterprise Release 6.2

2 DeviceAnywhere Enterprise 6.2 DeviceAnywhere Enterprise 6.2 February 2014 Copyright Notice Copyright Keynote Systems, Inc. All rights reserved THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED AS IS WITHOUT ANY EXPRESS REPRESENTATIONS OF WARRANTIES. IN ADDITION, KEYNOTE DISCLAIMS ALL IMPLIED REPRESENTATIONS AND WARRANTIES, INCLUDING ANY WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT OF THIRD PARTY INTELLECTURAL PROPERTY RIGHTS. All text and figures included in this publication are the exclusive property of Keynote and may not be copied, reproduced, or used in any way without the express permission in writing of Keynote. Information in this document is subject to change without notice and does not represent a commitment on the part of Keynote. Keynote may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents except as expressly provided in any written license agreement from Keynote. The trademarks or registered trademarks of Keynote Systems, Inc. in the United States and other countries include Keynote, DataPulse, CustomerScope, Keynote Customer Experience Rankings, Perspective, Keynote Red Alert, Keynote WebEffective, The Internet Performance Authority, MyKeynote, SIGOS, SITE, keynote The Mobile & Internet Performance Authority, Keynote FlexUse, Keynote DeviceAnywhere, DeviceAnywhere, Keynote DemoAnywhere, Keynote MonitorAnywhere. All related trademarks, trade names, logos, characters, design and trade dress are trademarks or registered trademarks of Keynote Systems, Inc. in the United States and other countries and may not be used without written permission. All other trademarks are the property of their respective owners. Please forward any comments or suggestions regarding this document to Keynote Support. Keynote Systems, Inc. 777 Mariners Island Blvd. San Mateo, CA ii Keynote Confidential

3 DeviceAnywhere Enterprise 6.2 Contents 1 Overview New Features BETA Features... 6 Native Object-Level Scripting on ios Devices... 6 Limitations and Suggestions for ios Object Scripting BETA... 7 Web Element-Based Scripting in Hybrid Applications... 7 Limitations and Suggestions for Web Element Scripting in Hybrid Apps BETA Updates Resolved Issues Known Issues Keynote Confidential iii

4 DeviceAnywhere Enterprise Overview This release of DeviceAnywhere Enterprise is for shared and standalone deployments with BETA offerings of the ability to create native object scripts on ios devices and also script for web elements in hybrid applications. Device interaction improvements include easy issue reporting and the ability to upload applications onto Windows 8 devices and non-jailbroken ios devices. 2 New Features Application Upload for Non-Jailbroken ios Devices Users can now upload applications onto shared non-jailbroken ios devices and have the applications signed using Keynote s enterprise certificate. In the device console s Applications tab, there several upload options when you select Add Application. Choose the iphone application Type and then click Advanced. Figure 2-1 Application Upload UI Sign Application (default) Signs application with Keynote s certificate and uploads it to your application repository from where you can deliver it to any ios device. Upload As Is Uploads the application without signing with the Keynote certificate. Before uploading the application for delivery to a non-jailbroken device, make sure to sign it with your own enterprise certificate or provision to the target UDID and sign with your individual developer certificate. Sign & Enable Application Signs the application and inserts libraries that enable object-based scripting for native applications as well as testing of web elements in hybrid applications. You can also use this interface to upload applications to jailbroken ios devices. 4 Keynote Confidential

5 DeviceAnywhere Enterprise 6.2 NOTES Application upload for non-jailbroken ios devices is limited to.ipa files. Application.zip files in the repository cannot be delivered to non-jailbroken devices. Users with on-premise devices should contact the Keynote Solutions Consultant for signing and enabling applications. ios 7 devices need to have the latest version of itunes to upload applications. Object testing of native applications or web elements in hybrid applications on is not available on ios devices in the shared system. Application Upload for Windows 8 Devices The ability to upload to the repository and deliver applications to Windows 8 devices is now available. Be sure to choose Windows Phone 8 as the application Type when uploading to the repository. Figure 2-2 Uploading Applications for Windows Phone 8 Reporting Device Issues Reporting a device issue is now easier from DeviceAnywhere Studio. When you right-click a device and select Report an Issue, you are presented with a dialog box to choose the issue type, enter any details, and directly submit a ticket. The device MCD is automatically captured for the ticketing system. Keynote Confidential 5

6 DeviceAnywhere Enterprise 6.2 Figure 2-3 Reporting a Device Issue 3 BETA Features Native Object-Level Scripting on ios Devices You can now use commands in the Object category to interact directly with objects in native applications on ios devices with OS version 5.0 or higher. Figure 3-1 Object Commands Prerequisites for Object-Level Scripting: Devices and test applications must be configured for this feature to work. Works on ios devices with OS 5.0 or higher. Available only by request please contact your Keynote Solutions Consultant. ios devices require the DeviceAnywhere Agent. Test native applications must be enabled for object-level scripting by inserting libraries and signing with Keynote s enterprise certificate. You can do this by using DeviceAnywhere Studio to upload and deliver your native application to the device choose the Sign and Enable option. See Application Upload for Non-Jailbroken ios Devices Error! Reference source not found.. Users with on-premise devices should contact the Keynote Solutions Consultant for signing and enabling applications. 6 Keynote Confidential

7 DeviceAnywhere Enterprise 6.2 Limitations and Suggestions for ios Object Scripting BETA Object commands in DeviceAnywhere Studio work with ios objects from the UIView class or its subclasses. The DeviceAnywhere Agent on non-jailbroken ios devices might need to be restarted to establish a connection or if you are unable to view the objects of your instrumented application. You might also need to restart the Ensemble Server if you are unable to see device video. You might also experience issues viewing streaming video. If you are unable to see video after reconfiguring a device, release the device and reacquire it. It is recommended that you close all other applications before object-level scripting on your enabled ios application. You cannot use the Launch App and Close App commands to launch/close native applications on ios devices you can, however use commands such as Find and Touch for this purpose. Unlike on Android, only objects in the enabled application can be extracted. After being enabled for object-level scripting, ios application objects are assigned index numbers. Index numbering can be assigned differently depending on the application. In some applications, index numbering can start at the bottom of the screen while in others it can start at the top. Objects are identified and extracted by index number, leading to the possibility that the same index number can be found on different pages. To avoid false positives, verify another object by text on the same page. Web Element-Based Scripting in Hybrid Applications Users can now use Web category commands to interact directly with web elements in hybrid applications. Figure 3-2 Web Commands Prerequisites for web element scripting in hybrid applications: Devices and test applications must be configured for this feature to work. Works on shared Android devices with OS or higher that have already been set up for native object testing. This feature requires the DeviceAnywhere Agent. The test hybrid application must be enabled by adding libraries that auto-inject Javascript code to web pages in the application. You can do this by using DeviceAnywhere Studio to upload and deliver your hybrid application to the device choose the Sign & Enable Application option. Keynote Confidential 7

8 DeviceAnywhere Enterprise 6.2 Works on dedicated ios and Android devices. Users with on-premise devices should contact the Keynote Solutions Consultant for signing and enabling applications. Limitations and Suggestions for Web Element Scripting in Hybrid Apps BETA Web element testing in hybrid applications is not available on ios devices in the shared system. You cannot use the Launch App, Close App, Browser Open, or Close All Browser Sessions commands to launch/close applications or the browser on ios devices you can, however use commands such as Find and Touch for this purpose. Only one hybrid application can be open on a device at a time. If you need to close your hybrid app mid-script and open a different web application in the browser, be sure to insert steps to force close your hybrid app. 4 Updates Updating Object Layout in Commands Object commands now have a camera icon to update object layout when you switch from one device screen to another. The Auto-Update Layout check box is no longer available. 8 Keynote Confidential

9 DeviceAnywhere Enterprise 6.2 Figure 4-1 Updating Layout in Object Commands Click to update layout Object layout in command Swiping to Select an Object in Object Touch When you implement a swipe in Object Touch to bring an object into view before selecting it, you can now specify how much of the object must be visible before it is selected or touched. Specify a percentage in the Margin Percent flag of the Advanced tab. Then run the command to see whether the object is correctly selected. If not, increase the percentage of the object that must be visible before it is touched. Figure 4-2 Margin Percent Flag Updated Device Information In the advanced device search available by clicking the filter icon, you can now search by minor OS version (e.g., Android 4.0.x) or by any of our supported carrier networks. Keynote Confidential 9

10 DeviceAnywhere Enterprise 6.2 NOTE Searching by minor OS version has always been supported by typing into the free-form text Filter field. Figure 4-3 Advanced Search by Minor OS Version and Carrier Network 5 Resolved Issues Opening Hybrid Apps on Android After using Launch App to open a hybrid application on an Android device, users had to insert wait time to allow the auto-injection of Javascript required for the script to work. This is no longer required. PhoneGap Applications PhoneGap hybrid applications can now be enabled for web element-based testing. Swiping in ios Object Commands An issue with swiping ios devices when using Object commands has been fixed. Selecting Objects Correctly During Execution An issue with pop-over advertising banners or keyboards causing native objects not to be selected correctly during script execution has been resolved. Exporting Frames from Video History Video history for longer device sessions no longer takes a long time to load (right-click device > Export Frames > Video from history). Note, however, that generating a video from history for export to your file system will take time. Device Reservations Issues with device reservation in the DeviceAnywhere Enterprise shared system prevented users from acquiring a reserved device. This issue has now been resolved. 10 Keynote Confidential

11 DeviceAnywhere Enterprise 6.2 Editing Java Scripts Simultaneously in DeviceAnywhere Studio and an IDE A Java test script that was open in DeviceAnywhere Studio and simultaneously edited in an external editor was not refreshed in DeviceAnywhere Studio. This issue has been resolved; you no longer have to close and reopen the project as a workaround. Using Web Form An issue with the <form> element not being displayed in the Web Form command when working with a form on a device has been resolved. Inspect Mode Issues Issues with inspecting invisible elements have been fixed. If you try to inspect an invisible element in a Web command, DeviceAnywhere Studio does not go into inspect mode. Video Proof with Audio Issues with capturing audio as part of video proof have been resolved; audio is being correctly captured in uploaded or exported video proofs. If you are still unable to hear audio in video proofs, upgrade your codec or use a different media player. 6 Known Issues Data Sets in Object Touch Data set variables are not listed when you click Choose Variable in the Object Touch command. Non-Jailbroken ios Agent Issues Ensemble restart is required after onboarding or reconfiguring a non-jailbroken ios with the new Agent in order for device logging to work. Installing the DeviceAnywhere DOM Server You can only install the DeviceAnywhere DOM Server on 64-bit machines. If you choose an installation path that has spaces, the service does not get installed correctly. This issue is relevant for customers with dedicated, on-premise deployments. External Version Control Support for external version control systems is not available in this release. Clearing Browser Cache on Android Devices When using the Open Browser and Close All Browser Sessions commands on supported Android devices, users have the option of clearing the browser cache. Clearing browser cache resets all browser settings to default values, e.g., dialog boxes to save passwords for web sites are displayed, security warnings are displayed, and bookmarks are erased. The Clear browser cache option also closes existing browser sessions and deletes cookies. Users must register the device MCD with the Central Server again at Closing Android Browser Sessions Android browser sessions cannot be closed using the Browser Open command s Close any existing browser sessions options. However, the Browser Open command s Clear browser cache option also closes all browser sessions (in addition to resetting the browser to default settings). Keynote Confidential 11

12 DeviceAnywhere Enterprise 6.2 The Close All Browser Sessions command closes browser sessions (Clear browser cache must be checked) on Android 4.0.x and higher devices. Using a Variable in Place of Attribute Value in Web Form When you choose a variable for the Attribute Value in Web Form, search results are not displayed, i.e., no <form> element is listed, and you cannot work with its fields. As a workaround, first select or enter a value you wish to use in order to set up the command and then switch to a variable. Web Command Recording Web command recording in DeviceAnywhere Studio is supported only on ios 6 devices. Inserting and defining Web commands is available on all supported platforms. Viewing the DOM in Results When viewing uploaded results for a Web command in the portal, opening the DOM in a separate browser window by clicking Open in browser mode is supported on Internet Explorer, but not Mozilla Firefox or Google Chrome. Setting MCD for Applications For testing web applications in the DAE shared environment, to make sure that the MCD is set properly, use the Browser Open command, or manually navigate to the set MCD page ( and enter the device MCD. Waiting for Web Elements or Native Objects in Wait Event If you have multiple branches based on image-, text-, web element-, and object-based reference points in Wait Event, objects can take up to 30 seconds to be matched. As a workaround, use a separate Wait Event command for object-based reference points and a separate Wait Event command for web element reference points. When creating multiple events in the Wait Event command, the Web Wait option can take the entire timeout to complete successfully. Native objects selected in Wait Event are not highlighted when you reopen command. However, the script is executed as expected. Slot Names for Multi-Device Test Cases When you change slot names in test case properties for a multi-device test case, changes do not appear when you attempt to associate a script command to a slot (right-click command > Device Association). However, slot color codes are correctly displayed. To view the correct slot names, close and reopen your test case. Running in Debug Mode When you run a script in debug mode (Advanced > Run in Debug Mode), any embedded scripts are not opened in separate tabs as they are being executed. Excluded Devices in Scheduled Test Cycles When you exclude devices from a test cycle schedule, e.g., by specifying that only 1 of 2 test cases should run on 1 of 3 devices, you still receive execution s for the excluded devices. The portal displays no results available for those excluded devices, meaning that the test cycle is not actually executed on the excluded devices. 12 Keynote Confidential

13 DeviceAnywhere Enterprise 6.2 Shutting Down DeviceAnywhere Studio If you are not able to exit DeviceAnywhere Studio or even close the application window, use the Windows Task Manager to end the DeviceAnywhereStudio.exe process. Keynote Confidential 13