https://github.com/raghavendra-vaidya/vivid

Mobile app automation using appium, java
https://github.com/raghavendra-vaidya/vivid

appium appium-java mobile-app-automation mobile-app-testing

Last synced: about 6 hours ago
JSON representation

Mobile app automation using appium, java

• Host: GitHub
• URL: https://github.com/raghavendra-vaidya/vivid
• Owner: Raghavendra-vaidya
• Created: 2022-05-30T07:48:35.000Z (over 2 years ago)
• Default Branch: main
• Last Pushed: 2022-12-25T14:36:50.000Z (about 2 years ago)
• Last Synced: 2024-11-13T00:13:11.779Z (2 months ago)
• Topics: appium, appium-java, mobile-app-automation, mobile-app-testing
• Language: Java
• Homepage:
• Size: 27.1 MB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# vivid

Mobile app automation framework using appium-java bindings. :iphone:

Step 1: start appium server

Step 2: Start emulators

Step 3: Run tests

---

Run tests in parallel:

Approach no 1: Testng parallelism

Approach no 2: Appium grid and selenium grid

---

Combinations:

Android:

1. Multiple emulators

2. emulator + real devices

3. Multiple devices

iOS:

1. Multiple simulators

2. simulator + real devices (Out of scope rite now)

3. Multiple devices(Out of scope rite now)

---

![img.png](img.png)

---

Key points to note:

1. `systemPort` The number of the port the UiAutomator2 server is listening on. 

    By default, first free port from 8200..8299 range is selected. It is recommended to set this value if you are running parallel tests on the same machine.

2. URL of appium server session should have `wd/hub`

3. Parameter names from testng.xml should be same in method,  if you are achieving parallelism from testng.xml

4. providing path for `app` capability: fetch user.dir and combine user.dir with path of apk from content root to form absolute path. Relative path does not work here.

5. Capability type for emulators is `avd` we can also use `deviceName` as well.