Update Google Play Services and some other useful stuff by adb

This commit is contained in:
App-Test 2018-07-30 16:19:05 +04:30
parent 460e0b8daf
commit de71e5156c

View file

@ -12,7 +12,7 @@ Docker-Android is a docker image built to be used for everything related to mobi
<p align="center">
<a href="https://youtu.be/pQdpjuYwvp8"><img src="./images/appiumconf2018.png" alt="Appium Conference 2018" width="600"></a>
</p>
</p>
Emulator - Samsung Device | Emulator - Nexus Device | Real Device
:---------------------------:|:---------------------------:|:---------------------------:
@ -144,6 +144,14 @@ There is [example of compose file] to run complete selenium grid and docker-andr
```bash
docker-compose up -d
```
### Google Play Services
The Google play services (v12.8.74) will be downloaded from [apklinker](https://www.apklinker.com/wp-content/uploads/uploaded_apk/5b51570a214a8/com.google.android.gms_12.8.74-040700-204998136_12874026_MinAPI23_(x86)(nodpi)_apklinker.com.apk) in src/utils.sh file when emulator booted . you can edit utils.sh as you need any adb stuffs and mount it as follow in docker-compose file :
volumes:
- $PWD//videos:/tmp/video
- $PWD/src/utils.sh:/root/src/utils.sh
or when run directly
docker run --privileged -d -p 6080:6080 -p 4723:4723 -p 5554:5554 -p 5555:5555 -v $PWD/src/utils.sh:/root/src/utils.sh -v $PWD/example/sample_apk:/root/tmp -e DEVICE="Nexus 5" -e APPIUM=true -e CONNECT_TO_GRID=true -e APPIUM_HOST="127.0.0.1" -e APPIUM_PORT=4723 -e SELENIUM_HOST="172.17.0.1" -e SELENIUM_PORT=4444 --name android-container butomo1989/docker-android-x86-8.1
Build Android project
---------------------
@ -181,9 +189,9 @@ Genymotion
![Genymotion](images/logo_genymotion.png)
Docker-Android supports [Genymotion Cloud].
Docker-Android supports [Genymotion Cloud].
You can easily scale your Appium tests on Genymotion Android virtual devices in the cloud.
You can easily scale your Appium tests on Genymotion Android virtual devices in the cloud.
Use [device.json] to define the device to start. You can specify the port on which the device will start so you don't need to change the device name in your tests every time you need to run those tests. Then run following command
```bash
@ -279,7 +287,7 @@ The following instructions are used for OS X. You'll need [docker-machine-parall
```bash
$ docker-machine create --driver=parallels prl-dev
```
This utility `docker-machine-parallels` will fetch boot2docker.iso to create a vm of VMWare fusion or Parallels Desktop. When the vm is created, you'll see it's booted with VMWare fusion or Parallels Desktop where the network of vm is set to NAT and one IP is assigned. You'll be able to connect to vnc service inside the docker image through that IP. Say it's `10.211.55.3` and we'll use it later.
3. Setup the virtual machine for nested virtualization support
@ -290,11 +298,11 @@ The following instructions are used for OS X. You'll need [docker-machine-parall
```
If you use VMWare Fusion, go to menu bar > Vitual Machine > Settings > Processors and Memory, expand Advanced options, and select `Enable hypervisor applications in this virtual machine`.
![Enable nested virtualization for VMWare Fusion](images/vmwarefusion_enable_nested_virtualization.png)
If you use Parallels Desktop, open settings screen of that vm and go to `CPU & Memory` under `hardware` tab, expand Advanced settings and select `Enable nested virtualization`.
![Enable nested virtualization for Parallels Desktop](images/parallels_enable_nested_virtualization.png)
4. Enable kvm inside virtual machine