In this version, we are happy to introduce more new products as well as new functionalities and features designed to help you release better quality mobile applications, faster.
Perform end-to-end mobile test automation directly from within your IDE with the new Eclipse Plug-in for Mobile Testing. The plug-in brings unprecedented simplicity to test automation with a single, powerful tool for developing Appium/Selenium mobile tests, and mobile test automation frameworks.
Appium Studio now supports all native Appium or Selenium clients allowing you to run tests developed on any platform without any code or dependency changes.
In addition, SeeTest 10.9 comes with numerous features and improvements designed to enable more effective testing and better efficient resource utilization.
|Table of Contents|
Main Release Highlights:
Eclipse Plugin for Mobile Testing - Free trial
Eclipse Plugin for Mobile Testing is a single tool for developing and executing Appium/Selenium mobile tests and automation frameworks.
Easily develop, automate, analyze and debug your mobile tests right in Eclipse, on remote physical devices. Rich views and editors help you speed up the development of robust tests and stable automation. The Plugin supports Appium, Selenium and SeeTest.
Use Eclipse Plug in for Mobile Testing to easily update existing tests and automation projects, or create new ones
- Native Eclipse plug-in providing a rich test development and automation environment right in Eclipse.
- Rich views and editors including device reflection, application manager, object repository editor, parallel execution wizard and more.
- Streamlined development of robust and maintainable tests for all mobile OS with advanced object identification tools including a dynamic device reflection, object repository with dynamic identification and more
- Develop test scripts for all mobile OS using unique test development tools such as a drag and drop script editor or scripts “story” view
- Verify and analyze tests executions with element highlighting and offline analysis
- Automate any mobile application scenario by fully controlling remote mobile devices
- Cover any application type and any use case, including complex out-of-app use cases
- Integrate seamlessly into existing testing and continuous integration environments
- Perform large-scale parallel execution using SeeTestGrid
- Detailed reports for rapid feedback and resolution
- Simple first user flow
Automation is performed on remote devices, using a mobile device lab at your own premises or hosted at Experitest datacenter
[Eclipse Plugin for Mobile Testing, SeeTestCloud]
Appium Studio is now client agnostic, supporting all native Appium or Selenium clients.
Use Appium Studio to run tests developed on any platform without any code or dependency changes. Tests developed in Appium Studio can also be run in any Appium server.
[SeeTestGrid, Appium Studio]
Remote devices can now be opened in debugging mode with a single click directly from SeeTestManual.
Perform remote debugging on Android or iOS applications with a single click. Remote debugging speeds up error resolution by allowing developers to debug on the device where the error occurred, speeding up root cause analysis by removing the guesswork involved in recreating exact error conditions.
|1||Android - retrieve battery info only if requested||SeeTest Web Studio testers can now choose whether they wish to retrieve and log battery info. This improves battery life and saves resources.||Improvement|
|2||SeeTest Automation - connect to grid with Java based test scripts||SeeTest Automation now features a checkbox in the code export section that, when checked, adds the relevant code lines in order to allow a tester to run tests in the Grid.||Improvement|
|3||SeeTest Cloud - adding log devices to support data when running tests in the cloud||SeeTest Cloud now allows testers to add the device logs to when collecting support data Docs||Improvement|
|4||iOS - launching and running a test even if the device is locked||Testers can now launch and run tests on locked devices. When launching a test on a locked device, the device will open and the test will run as intended.||Improvement|
|6||SeeTest Cloud - improving performance where large lists are present.||Improving performance and usability where large lists are present in different views in the cloud (users, projects, devices).||Improvement|
|7||iOS Safari - working with tabs||SeeTest now allows testers to retrieve the IDs of opened tab and perform actions on such tabs.||Improvement|
|9||SeeTest Cloud - keep the device in reserve mode after releasing the grid client||SeeTest Cloud now implements an option, through the test script, to keep the device in reserved mode even if the Grid Client was released. This ensures that the device will remain reserved for a given tester for consecutive tests, ensuring productivity and workflow.||Improvement|
|10||SeeTest Cloud and SeeTest Automation for Web - supporting VBScript||SeeTest Cloud now supports VBScript when connecting to a session using SeeTest Automation for Web.||Improvement|
|11||Increased CPU usage when capturing Android screenshot||Improved handling of Android screenshots, leading to decreased usage of CPU and better performance.||Bug|
|12||Appium Studio - cannot connect to cloud devices||Making sure Appium Studio identifies and connects to devices in the cloud.||Bug|
|13||Unclear messages when test session is interrupted||Providing clearer, more relevant error messages to notify the tester of the cause of the disruption.||Bug|
|14||SeeTest iOS - device is not opened automatically after reboot||Making sure that the device opens automatically once reboot is done and the device is up and running again.||Bug|
|15||Support iOS 10.3.2 beta 5||Providing full support across products for iOS 10.3.2 beta 5.||Bug|
|16||Appium Studio - changing screen orientation not supported||Providing full support for changing and handling device orientation changes.||Bug|
|17||Android - opening an app with camera functionality crashes the app||Handling app permissions so that the tested app has access to and can utilize camera functionality.||Bug|
|18||iOS - iMessage Plugin disrupts element structure in object spy||Making sure that the element tree structure is unaffected when testing iMessage plugins.||Bug|
|19||iOS - fix get device category||Making sure the correct string representing the category (phone or tablet)||Bug|
|20||iOS - extend simulate capture functionality||Aligning support with Apple's AVFoundation framework to support camera functions.||Bug|