Articles Tagged 'mobile'

Rapise connects to mobile devices (iOS and Android) using the standard Appium mobile device testing API (similar to Selenium WebDriver for web browsers). This articles describes how you can use Rapise to connect to a mobile device farm using the Appium mobile device profiles inside Rapise. We use Kobiton as an example.

Most complex part in Mobile testing is connecting to a simulator or device. In this article we describe steps necessary to configure the testing environment.

Note: In brackets we specify versions of software components we used at the time of writing this article.

When testing mobile applications, you may need to draw graphics, such as a signature. This article provides a helper function that you can copy and customize for your tests.

Sometimes mobile testing scenarios involve interactions with built-in applications installed on a device. For example you may need to open Messages, locate SMS with a one-time code and use it in your application.

BrowserStack enables you to test image capture and QR/Bar code scanning from BrowserStack’s mobile device camera. If your mobile app has features, such as check scanning, profile image capture, and QR/Bar code scanning, you can use this feature to automate the testing of such a feature in your app.

This is the second part of the iOS Testing Hints series. It describes how to configure real device testing if you dp not have a paid membership with Apple Developer.

Most complex part in Mobile testing is connecting to a simulator or device. In this article we describe steps necessary to configure the testing environment.

Note: In brackets we specify versions of software components we used at the time of writing this article.

Ionic is an open source UI toolkit for building performant, high-quality mobile apps using web technologies — HTML, CSS, and JavaScript. This means that being mobile, Ionic applications are web applications by nature. And it is much more convenient to test them via WebDriver rather than Appium. Requires Rapise 8.1+.

You may receive an .ipa file from a development team or download one published by a third-party vendor. In order to create and run automation scripts using a real iOS device you need to resign the .ipa file with your provisioning profile and development certificate. Learn how to do it from this article.

Sometimes when recording a test against a mobile responsive web site, it is useful to be able to record on the local browser (before playing it back against a cloud service such as SauceLabs, Browserstack, etc.). However you want to always record using a specific browser window size.

Yes, in general, Rapise can automate most web applications using mobile Safari running on iOS (either on a real or simulated device). However there are some limitations.

This article is obsolete. The recommended way of testing Web applications is to record tests on a desktop browser via Selenium-based profile and then execute using Mobile profiles. See How to run a cross-browser test on a mobile device for more details.

We often get asked this question: "We have Rapise and want to automate a native iOS app that is available on the application store", can we do it?

We have had a couple of questions about whether Rapise can test Adobe AIR based applications running on mobile devices using platforms such as Android. This article provides some background and also describes the support Rapise has.

[We have depreciated support for testing Adobe Flex/Flash applications in Rapise 5.0 and later, so this article is provided for use by existing customers]

Sauce Labs allows users to run tests in the cloud on different combinations of browser and OS versions as well as mobile devices and emulators. Learn how to configure Selenium and Mobile profiles in Rapise to enable connection to Sauce Labs services.

Requires Rapise 5.3+

If you receive the following error message when performing Mobile device testing with Rapise, this article provides the necessary solution:

Method not found:
'OpenQA.Selenium.RemoteCommandInfoRepository
OpenQA.Selenium.RemoteCommandInfoRepository.get_Instance()'.

Note: related to Appium DLL version  1.3.0.1 and  Selenium WebDriver v2.48.0.

Bitbar is a browser and device farm that enables it's clients to run cross-browser and mobile tests remotely.

Since version 6.3 Rapise has support for local browser and mobile profiles. Using it you may package browser profiles along with tests. What if you want to reuse browser profiles between different projects? Or have sets of profiles for different situations? You may now set path to profile directory using a special global variable.  Supported in Rapise 6.4+

From this article you will learn how to pass additional parameters to Selenium or Appium target, even if they can not be specified in a profile.  This recipe can be also used to override parameters of a profile right from a test code.

Requires Rapise 5.3+

Most complex part in Mobile testing is connecting to a simulator or device. In this article we describe steps necessary to configure the testing environment.

Note: In brackets we specify versions of software components we used at the time of writing this article.

When Appium installs an application at the beginning of a test session - Android may ask for permissions (e.g. access to media files, camera, etc.). Until such prompt is dismissed - Main activity is not launched. It prevents the test from proceeding.  Learn how to configure the Mobile Profile to automatically grant required permissions on install.

Let's assume you have a cross-browser test which was created on desktop and can be successfully executed on any desktop browser (Chrome, Firefox, Internet Explorer, Safari). You want to execute this test on your mobile devices or emulators. Learn how from this article.

Requires Rapise 5.3+