Видео

There are two ways to start appium server 1. programmatically check video in playlist 2 . Using appium desktop server ruclips.net/video/P9FegRIOkg0/видео.htmlsi=PI_C1LXIkMobJFOj

Thnx for your support 🙏

When automating multiple app interactions using Appium, switching between apps can be challenging. The issue you’re facing occurs because Appium maintains a single active session per app. To handle such scenarios, you need to use the startActivity() method or manage multiple driver instances.

Launch App A and perform actions to create an order. 2. Use the driver.startActivity() method to switch to App B without terminating the App A session. 3. Perform actions in App B to accept and reallocate the order. 4. (Optional) Switch back to App A if needed.

@ thanks for quick response .. i am using appium 9.3.0 version and driver.startActivity() is not supported . Can you please some alternative for this. I am using driver.executeScript(“mobile:startActivity”, appPackage/.appActivity) still didn’t get any success

Map<String, Object> args = new HashMap<>(); args.put("appPackage", "com.example.package"); // Replace with your app package args.put("appActivity", ".MainActivity"); // Replace with your app activity driver.executeScript("mobile:startActivity", args); Try this once and let us know

Sure please clarify more

Check if you’re using the latest Appium version. Older versions might not support certain capabilities.

Thanks for your feedback

Thanks for your support and valuable feedback 🙏

1. Use KeyEvent for the SHIFT key: Send a KEYCODE_SHIFT_LEFT event before sending the letter key. For example, to type an uppercase “A”, press KEYCODE_SHIFT_LEFT followed by KEYCODE_A. Here’s a sample code snippet in Java: // Press SHIFT key ((AndroidDriver) driver).pressKey(new KeyEvent(AndroidKey.SHIFT_LEFT)); // Press "A" key ((AndroidDriver) driver).pressKey(new KeyEvent(AndroidKey.A)); // Optionally release the SHIFT key ((AndroidDriver) driver).pressKey(new KeyEvent(AndroidKey.SHIFT_LEFT).withAction(KeyEvent.ACTION_UP)); 2.Alternative Approach - Use sendKeys: If pressKey doesn’t work consistently, consider using sendKeys on the input field directly, as it allows sending uppercase letters without needing to handle shift keys. driver.findElement(By.id("your_element_id")).sendKeys("A");

Thank you ☺️

Thank you for your support 🙏

Thank you so much for your support

Sure can you share error

Thank you so much for your Valuable Feedback

Thank you for your great feedback 👍

Sure will add this session

Thanks for your valuable comment 🙏

Share what logic you implemented.?

Thank you keep watching 👀

Thanks so much for great feedback 🙏

Thank you so much for this kind of support and beautiful comment.🙏

Thank you for your valuable feedback

Thanks for your support

Default Name is emulator 5554

@@BhauAutomationLab ok got it thankyou

Please share error details.

Bcoz i have set app package name and activity name in desired capabilities.

@@BhauAutomationLab I have also set appPackage and apActivity in code still If I comment my apk path, my script fail

@OptionTrader91 Please share your caps details

@@BhauAutomationLab//Setting Desire Capabilities for device DesiredCapabilities caps = new DesiredCapabilities(); caps.setCapability("appium:automationName",AndroidAppAutomationName); caps.setCapability("udid", "emulator-5554"); caps.setCapability("appium:deviceName", "sdk_gphone_x86_64"); caps.setCapability("platformName", "Android"); caps.setCapability("appium:platformVersion", "13"); caps.setCapability("appium:app", "C:\\Users\\Rahul Sinha\\eclipse-workspace\\ClearQuoteInspection\\src\\test\ esources\\ClearQuote Inspections.apk"); caps.setCapability("appWaitForLaunch", false); caps.setCapability("appPackage", AndroidAppPackageName); caps.setCapability("appActivtiy", AndroidAppActivtiyName); URI url = new URI(AppiumURL); driver = new AndroidDriver(url.toURL(),caps);

Can you explain exactly requirements

@@BhauAutomationLab i have a website and created a selenium java script and we run the script on jenkins, now we want to run the same script on mobile browser(not trying app just on mobile browser Chrome) and should run on jenkins... So i have a question that should i go with appium or browserstack?

@atulbankar1486 To run mobile browsers like Chrome we required Appium, it doesn't matter if you are running scripts on BrowserStack or an Android emulator. BrowserStack is only a cloud service. If you have a BrowserStack account, run your tests on BrowserStack. If not, run them on an Android emulator. Let me know if you need any further assistance

@@BhauAutomationLab ok sir we have a browserstack account and i have written a script which is finely working on appium server and used a vysor tool for mobile screen view but for that need to connect personal mobile through usb..so is it posible to run the script on jenkins server?In browserstack, i think it provides a virtual mobile screen and it will become easy.. So i want your guidance.. What to do.. Go with appium or browserstack... As we are not testing for app just want to test website on mobile screen by opening a chrome browser..

@atulbankar1486 If you have browserstack account run your script on browser stack devices and chrome browser use Jenkins for cicd create schedulers as per your execution time.

Sure Thanks for your feedback

Sure Thank you for your valuable feedback

Coming soon

@@BhauAutomationLab Do you provide class??

@OptionTrader91 Please check contact details in about section facebook.com/SelemiumAppiumAPIAutomation

@@BhauAutomationLab thankyou

Sure coming soon thanks for update

Thank you so much for great feedback Will create sessions for IOS devices soon keep watching and learning ☺️

Thanks for your plz check your and below 1. This might work if the default URL is configured or when using a specific driver like AndroidDriver or IOSDriver. 2. Bcoz i have setup app package name and activity name capabilities in desired capabilities code.

Thank you ☺️

Thank you for your valuable feedback 👍

Thank you

Below are the examples for performing tap and long press actions using the `TouchAction` class and the W3C Actions API in Java with Appium 2.0. ### Using `TouchAction` Class 1. **Tap Action**: ```java import io.appium.java_client.AppiumDriver; import io.appium.java_client.TouchAction; import io.appium.java_client.touch.TapOptions; import io.appium.java_client.touch.offset.ElementOption; import org.openqa.selenium.WebElement; // Assuming 'driver' is your AppiumDriver instance and 'element' is the element to tap TouchAction action = new TouchAction(driver); action.tap(TapOptions.tapOptions().withElement(ElementOption.element(element))).perform(); ``` 2. **Long Press Action**: ```java import io.appium.java_client.AppiumDriver; import io.appium.java_client.TouchAction; import io.appium.java_client.touch.LongPressOptions; import io.appium.java_client.touch.offset.ElementOption; import org.openqa.selenium.WebElement; import java.time.Duration; // Assuming 'driver' is your AppiumDriver instance and 'element' is the element to long press TouchAction action = new TouchAction(driver); action.longPress(LongPressOptions.longPressOptions() .withElement(ElementOption.element(element)) .withDuration(Duration.ofSeconds(2))) // long press duration .release() .perform(); ``` ### Using W3C Actions API 1. **Tap Action**: ```java import org.openqa.selenium.WebDriver; import org.openqa.selenium.WebElement; import org.openqa.selenium.interactions.Actions; // Assuming 'driver' is your WebDriver instance and 'element' is the element to tap Actions actions = new Actions(driver); actions.moveToElement(element).click().perform(); ``` 2. **Long Press Action**: ```java import org.openqa.selenium.WebDriver; import org.openqa.selenium.WebElement; import org.openqa.selenium.interactions.PointerInput; import org.openqa.selenium.interactions.Sequence; import java.time.Duration; import java.util.Arrays; // Assuming 'driver' is your WebDriver instance and 'element' is the element to long press PointerInput finger = new PointerInput(PointerInput.Kind.TOUCH, "finger"); Sequence longPress = new Sequence(finger, 1); longPress.addAction(finger.createPointerMove(Duration.ZERO, PointerInput.Origin.viewport(), element.getLocation().x, element.getLocation().y)); longPress.addAction(finger.createPointerDown(PointerInput.MouseButton.LEFT.asArg())); longPress.addAction(new org.openqa.selenium.interactions.Pause(finger, Duration.ofSeconds(2))); // long press duration longPress.addAction(finger.createPointerUp(PointerInput.MouseButton.LEFT.asArg())); driver.perform(Arrays.asList(longPress)); ``` ### Setting Up Appium 2.0 with Java 1. **Install Appium 2.0**: ```bash npm install -g appium@next ``` 2. **Install Necessary Drivers and Plugins**: ```bash appium driver install <driver-name> appium plugin install <plugin-name> ``` 3. **Start Appium Server**: ```bash appium server ``` ### Maven Dependency for Appium Java Client Make sure to include the Appium Java client dependency in your `pom.xml`: ```xml <dependency> <groupId>io.appium</groupId> <artifactId>java-client</artifactId> <version>8.0.0</version> <!-- Ensure this is the latest version --> </dependency>

Thank you so much for your valuable feedback keep watching ☺️

1. Reinstall Android SDK Tools: Open your Android SDK manager. Locate the "Android SDK Tools" package and uninstall it. After uninstallation, reinstall the "Android SDK Tools" package. This should ensure the emulator program for x86 is properly installed. 2. Run Emulator with Full Path: Instead of just using "emulator-x86", try running the emulator with the full path to the executable. The path might be something like: */<path to your SDK>/*sdk/tools/emulator64-x86 -avd <your_emulator_name> 3. Check Emulator Path in Environment Variables: In some cases, the emulator path might not be set correctly in your environment variables. You'll need to consult your OS's documentation on how to edit environment variables and ensure the path to your emulator directory (e.g., */<path to your SDK>/*sdk/emulator) is included. 4. Use 64-bit Emulator (if available): If your development environment supports it, consider switching to a 64-bit emulator (x86_64). This might avoid the issue altogether, especially if 32-bit support (x86) is limited.

Yes, you can definitely use Cucumber example variables in scenario outline titles. The issue you're encountering with the scenario outline being skipped is likely due to Double-check your scenario outline and steps for any typos Make sure your step definitions for steps like add <num1> and <num2> are properly implemented to handle the dynamic values from the example table. Use below code Scenario Outline: Addition of <num1> and <num2> Given add <num1> and <num2> Then the result should be <sum> Examples: | num1 | num2 | sum | | 3 | 4 | 7 | | 5 | 6 | 11 |

@@BhauAutomationLab i see the following unders the test result on post run : Addition of <num1> and <num2> Examples Example#1 Example#2 <num1> and <num2> appears as the tags and not with values .. i expected something like Addition of 3 and 4 .............. Addition of 5 and 6 .............. i executed the feature file directly by rightclick

Thanks for your feedback

Thanks so much for great feedback