Document link - docs.google.com/document/d/e/2PACX-1vRnTmwDeynRlYUu9ib-jtkH7Ukas7TWyd0ww-aS6itEKjhXWCaGeI72fJ_0MIwrHG4oCK140Iv7iwBy/pub#h.eoqr2a4ylhfk
@HelenMunny6 ай бұрын
I tried several intructors in KZbin for QA. But you and Pavan are the only two for me... Thanks a ton for your support.
@RaghavPal6 ай бұрын
Glad to hear that Helen.. keep learning
@HiteshDarji-m5u7 ай бұрын
Waiting for this Appium 2 series for a long. Thank you so much bhai.
@RaghavPal7 ай бұрын
Most welcome Hitesh
@induminichamaransi49709 ай бұрын
Everything was very clear and easy to understand. Thank you. This is by far the best video I've come across regarding automation. ❤
@RaghavPal9 ай бұрын
Most welcome Indumini.. Thanks for the kind words.. humbled
@marwanm89427 ай бұрын
You deserve a thumb-up 👍for an awesome job and how you simplify things.
@RaghavPal7 ай бұрын
Thank you so much Marwan
@StanislavCertik7 ай бұрын
Love your tutorials, they are great start for begginers!
@RaghavPal7 ай бұрын
Thanks a lot Stanislav
@vivekpukale26248 ай бұрын
Thank you for clear instruction on setup😀 Waiting for next 1
@RaghavPal8 ай бұрын
Sure coming today evening Vivek
@venvedam8 ай бұрын
Thank you! Waiting for the next session!
@RaghavPal8 ай бұрын
Most welcome Ven. Coming tomorrow.. here.. kzbin.info/www/bejne/moe3i6Opg66Bg5o
@795ksrАй бұрын
Thanks a lot :), Appium doctor is much needed command😍
@RaghavPalАй бұрын
Yes Karthik
@user-benjaminJohn4 ай бұрын
Hi Raghav, I'm so happy you created this series. Appium needed a refresh. What is the web page you go to for ui testing? It has everything on it, radio buttons, check boxes, everything? 🙏🔥
@RaghavPal4 ай бұрын
Great to know this is helping Benjamin. I did not get you on the webpage thing... can you give the timestamp from the video
@bhrigumonibaruah251Ай бұрын
Brother, can I follow this playlist, or do I have to complete the first appium playlist?
@RaghavPalАй бұрын
Can follow this for latest appium 2 setup. After that in case you want to create framework in appium java can check the older one
@ollice34655 ай бұрын
This is very usefull. Keep it up sir. Thank you.😍
@RaghavPal5 ай бұрын
Always welcome
@fathimanazra12798 ай бұрын
Thank you , Waiting for next session
@RaghavPal8 ай бұрын
coming tomorrow Nazra, here - kzbin.info/www/bejne/moe3i6Opg66Bg5o
@Masheru144 ай бұрын
I need advice, should i choose native appium or katalon/selenium with plugin appium? From that, i have enough understand automate web with cypress JavaScript, so i am overwhelmed choosing tools for mobile
@RaghavPal4 ай бұрын
I totally understand your dilemma Choosing the right tool for mobile automation can be overwhelming, especially when you're already familiar with Cypress for web automation. Here's an analysis to help you decide between Native Appium, Katalon with Appium plugin, and Selenium with Appium plugin: Native Appium Pros: Officially supported: Appium is an open-source tool, and its native implementation is the most widely adopted and supported solution for mobile automation. Flexibility: Appium provides a flexible framework that allows you to write tests in various programming languages, including Java, Python, Ruby, and C#. Large community: Appium has a massive community of users and contributors, which means there are plenty of resources available, including documentation, tutorials, and forums. Cons: Steeper learning curve: Appium requires a good understanding of mobile automation concepts, and its native implementation can be complex to set up and maintain. More coding required: You'll need to write more code to implement tests, which can be time-consuming and error-prone. Katalon with Appium plugin Pros: Easy to use: Katalon is a commercial tool that provides a user-friendly interface and a more straightforward approach to mobile automation. Faster test creation: Katalon's plugin architecture and built-in features, such as object spy and recorder, make it easier to create tests quickly. Integrated reporting: Katalon provides built-in reporting and analytics, which can be useful for test result analysis. Cons: Commercial license: Katalon requires a commercial license, which can be a significant investment for individuals or small teams. Limited customization: While Katalon provides a lot of features out-of-the-box, it may not be as flexible as Native Appium when it comes to customization. Selenium with Appium plugin Pros: Familiarity: If you're already familiar with Selenium for web automation, using it with the Appium plugin can be a more comfortable choice. Similar API: Selenium's API is similar to Appium's, so you can leverage your existing knowledge. Cross-platform: Selenium supports multiple platforms, including web, mobile, and desktop. Cons: Not optimized for mobile: Selenium is primarily designed for web automation, and its mobile support may not be as robust as Native Appium or Katalon. Additional setup required: You'll need to set up the Appium plugin and configure it to work with Selenium, which can add complexity. Now, considering your background in Cypress and JavaScript, here are some additional factors to consider: JavaScript support: If you prefer to stick with JavaScript, Native Appium and Selenium with Appium plugin both support JavaScript as a programming language. Cypress-like experience: If you're looking for a similar experience to Cypress, Katalon's user-friendly interface and built-in features might be more appealing. Ultimately, the choice between Native Appium, Katalon with Appium plugin, and Selenium with Appium plugin depends on your specific needs, preferences, and goals. Here's a summary to help you decide: Native Appium: Choose if you want a flexible, widely adopted solution with a large community, but are willing to invest time in learning and setting up the framework. Katalon with Appium plugin: Choose if you prefer a more user-friendly, commercial solution with built-in features and reporting, but are willing to invest in a license. Selenium with Appium plugin: Choose if you're already familiar with Selenium and want to leverage your existing knowledge, but are willing to set up and configure the Appium plugin. I hope this analysis helps you make an informed decision -
@kk_kus9 ай бұрын
Hey thank you for posting video for version 2.x Personal request from my side to you please upload this series on regular basis.
@RaghavPal9 ай бұрын
I will try my best
@divyadoddagoudar51538 ай бұрын
@@RaghavPal please do upload this series on regular basis
@LoveISFake.8 ай бұрын
@@divyadoddagoudar5153 why.
@ahtishamali13099 ай бұрын
Your lectures are undoubtedly very informative and provide ample opportunities for learning. Could you please upload Masterclasses on Appium similar to the ones you did for Cypress? & Could you please explain how to implement Appium with Visual Studio Code?
@RaghavPal9 ай бұрын
Thanks Ahtisham .. I will plan on this
@Rajeshkumarmuruganantham5 ай бұрын
Could you please tell me, How to do that single machine to perform two various platform parallelly. like windows and mac.
@RaghavPal5 ай бұрын
Rajesh please explain your scenario in detail. what exactly are you looking for stepwise
@mohammedhfayaz99444 ай бұрын
Hi Raghav, i have watched all the appium play lists, in my case I need to automate the flutter Android and iOS app, can we follow the same steps for the flutter app automation? Or do we need to do anything additional for flutter app automation?
@RaghavPal4 ай бұрын
Hi Fayaz I have not tried flutter app but the basic setup steps will remain the same as shown in the video
@justbored3.142 ай бұрын
do you have a series with appium and winappdriver?
@RaghavPal2 ай бұрын
As of now on Appium only.. Can check all here - automationstepbystep.com/
@pavankumar-xb7nw7 ай бұрын
Raghav which program language is your explaining for appium?
@RaghavPal7 ай бұрын
Pavan in this series I have focussed on the complete setup of android and ios with appium that is independent of any language.. You will have to select one language when you start creating the project after the setup... In my earlier Appium series i used Java.. can check all here - automationstepbystep.com/
@rohitbhagat70683 ай бұрын
I am working on a flutter based app, I have completed most of the screens for automated testings, but sometimes face issues. I do resolve them. 1. There are only Xpaths, no resource id. 2. The app is Product based,(Smart fan and Smart Locks), and there is a device addition process. Cannot handle the Fames part. 3. Handled most of the non-element taps by perform actions. Need some help with the frames, part.
@RaghavPal3 ай бұрын
Rohit In Flutter, frames are essentially containers that hold other widgets. When automating tests, frames can be tricky to handle because they don't have a direct resource ID. However, we can use other strategies to interact with elements within frames Here's a step-by-step approach to handle frames in your Appium tests: Step 1: Inspect the Frame Element Use the Appium Inspector or the driver.getPageSource() method to inspect the frame element. Look for the frame's XPath and note its attributes, such as class, id, or any other unique identifiers. Step 2: Use XPath to Locate the Frame Use the XPath you obtained in Step 1 to locate the frame element. You can use the driver.findElementByXPath() method to find the frame // Assuming you're using Java WebElement frame = driver.findElementByXPath("//your-frame-xpath"); Step 3: Switch to the Frame Once you've located the frame, you need to switch to it using the driver.switchTo().frame() method. This will allow you to interact with elements within the frame driver.switchTo().frame(frame); Step 4: Interact with Elements within the Frame Now that you're within the frame, you can use the usual findElementBy methods to locate and interact with elements within the frame WebElement elementWithinFrame = driver.findElementByXPath("//element-within-frame-xpath"); elementWithinFrame.click(); Step 5: Switch Back to the Default Content After interacting with elements within the frame, don't forget to switch back to the default content using driver.switchTo().defaultContent(). driver.switchTo().defaultContent(); Example Code Here's an example code snippet that demonstrates the steps above: // Locate the frame element WebElement frame = driver.findElementByXPath("//your-frame-xpath"); // Switch to the frame driver.switchTo().frame(frame); // Interact with elements within the frame WebElement elementWithinFrame = driver.findElementByXPath("//element-within-frame-xpath"); elementWithinFrame.click(); // Switch back to the default content driver.switchTo().defaultContent(); Pls try and check --
@rohitbhagat70683 ай бұрын
@@RaghavPal thanks for the help, but seems like the switchTo. part is working while the frame() part is not accepted. I checked it with Appium Inspector and Android Studio Frame layout, There aren't frames for the part I have been asking your help. Sharing some detailes and images via mail. Do review them when you have time.
@RaghavPal3 ай бұрын
will need to check more on this
@LoveISFake.8 ай бұрын
Why 3 videos are hidden please make them open. Excellent explanation sir❤❤ keep uploading videos on mobile testing.
@RaghavPal8 ай бұрын
They are in the process Shailesh... will get soon
@LoveISFake.8 ай бұрын
@@RaghavPal Thank you so much sir for replying ❤️❤️❤️.
@hamzaakbar79846 ай бұрын
Great Series 👌 Can you Please make a series for Appium with Python?
@RaghavPal6 ай бұрын
I will plan Hamza
@hamzaakbar79846 ай бұрын
@@RaghavPal Thanks, can you please share some estimated time?
@RaghavPal6 ай бұрын
not sure on this.. can take some time.. as and when i have focussed time will plan
@0907sush7 ай бұрын
what is the best way to start mobile native app automation using Maven or Robot framework?
@RaghavPal7 ай бұрын
Sushma Starting mobile native app automation involves setting up a robust framework. Here are some steps to get you started: 1. Choose Your Tools: - Appium: An open-source test automation framework for native, hybrid, and mobile web apps. It supports iOS, Android, and Windows apps using the WebDriver protocol - Maven: A build automation tool that manages dependencies and compiles your code. - TestNG: A testing framework that allows parallel execution and easy test configuration. 2. Project Setup: - Create a new Maven project. - Configure the `pom.xml` file with dependencies for Appium, TestNG, and Allure Reports. 3. Appium Configuration: - Implement a configuration class that initializes the `AppiumDriver` instance based on desired capabilities. - Specify device information, platform details, app path, and other configurations. - Use runtime environment variables to dynamically create the driver for local or cloud-based devices. 4. TestNG Test Cases: - Create test classes with annotated methods representing different test scenarios. - Leverage the Page Object Model (POM) and create an abstract class at the screen level to handle common functionality between Android and iOS applications. - Use a business logic layer to handle logical parts of tests (e.g., entering data, validating results). 5. Test Data and Configuration: - Store test data and environment configurations in JSON files for better organization. - Implement a JSON reader to fetch data from files. 6. TestNG XML Configuration: - Create a TestNG XML configuration file to control the test runner and manage test suites. - Define test suites, specify test classes, and set test parameters in the XML file. - Use runtime environment variables to select the operating system (Android or iOS) for testing. 7. Test Context for Data Passing: - Use a test context object or container to hold shared data or objects across different test cases. - Pass information between test methods by storing and retrieving data from the test context. 8. Maven Build and Execution: - Run the Maven build command to compile the code and resolve dependencies. - Execute tests using the `mvn test` command, triggering the TestNG runner defined in the XML configuration. 9. Allure Reports Integration: - Integrate Allure Reports for better test reporting and visualization¹. Remember, adapt these steps based on your specific project requirements. Happy automating --
@0907sush6 ай бұрын
@@RaghavPal Thank you very much
@sabashaikh2410Ай бұрын
Hi Raghav sir, from past 1 week I am searching for Saucelabs tutorial, but I am not getting the tutorial for the latest version of Saucelabs with Appium. I saw this series, but it is regarding Appium+Android studio. Can you please create 1 series with Appium+ Saucelabs. I am not able to properly understand the Saucelabs because all the videos are showing old versions of Saucelabs 🙏
@RaghavPalАй бұрын
Sure Saba I will plan on this. In case you need something urgent you can check saucelabs documentation for appium - docs.saucelabs.com/mobile-apps/automated-testing/appium/quickstart/
@abhishekgoel-be5yg5 ай бұрын
Hi, Raghav thanks for such detailed information. I just saw you uploaded appium 2 also. I was watching appium 1 video od yours and I have done setup till tutorial 6 ( How To Connect Real Android Device On Mac OS) for mac os. Did I miss anything new which is here ?
@RaghavPal5 ай бұрын
Abhishek If you are able to follow and implement it ,. it's great can continue. will suggest to watch Appium2 playlist as well as there are few changes
@abhishekgoel-be5yg5 ай бұрын
@@RaghavPal I used java version 8. Is that fine?
@RaghavPal5 ай бұрын
should be okay if that meets all other requirements of your project
@bhrigumonibaruah251Ай бұрын
Sir, what is the difference between your first Appium series and this series? Can I follow this series, or do I have to complete the first series and then follow this? Please help me out.
@RaghavPalАй бұрын
This is Appium 2 the latest release of appium. You can directly start with this series and if you need to create a framework after the setup can watch from earlier series
@PlusePop8 ай бұрын
Thanks Raghav.... Now this is super clear end to end i have a current issue Raghav I just joined a company as a solo qa engineer... But now we are currently faced with an issue a s the back end admin is facing downtime, load time issues... I have 2 years of experience in qa, but the companies I have worked with, barely faced these issues... Kindly help... How do I tackle this (my job is on the line)
@RaghavPal8 ай бұрын
Facing backend admin downtime and load time issues can be challenging, especially when you're the sole QA engineer. Let's break down the situation and explore some steps to tackle it: 1. Assess the Situation: - Understand the severity of the issue. Is it affecting critical functionality or causing significant delays? - Gather information about the specific symptoms, error messages, and patterns of downtime. - Communicate with the backend team to get insights into the root cause. 2. Identify Potential Causes: - Server Load: High server load can lead to performance issues. Check if the backend servers are overloaded - Bugs or Code Issues: Investigate whether there are any recent code changes that might be causing issues. - Database Performance: Slow database queries can impact load times. - Infrastructure: Consider factors like network latency, server configuration, and resource allocation. 3. Load Testing: - Perform load testing to simulate heavy traffic and identify bottlenecks. - Use tools like JMeter or Gatling to stress-test the backend. - Monitor server resources (CPU, memory, disk I/O) during load testing. 4. Review Backend Code: - Collaborate with developers to review backend code. - Look for inefficient queries, loops, or resource-intensive operations. - Optimize code where necessary. 5. Database Optimization: - Optimize database queries by adding indexes, avoiding unnecessary joins, and using caching. - Consider database sharding or partitioning if data volume is high. 6. Caching Strategies: - Implement caching mechanisms (e.g., Redis, Memcached) to reduce database load. - Cache frequently accessed data to improve response times. 7. Monitoring and Alerts: - Set up monitoring tools (e.g., Prometheus, Grafana) to track server performance. - Configure alerts for abnormal behavior (e.g., high CPU usage, memory leaks). 8. Scalability and Redundancy: - Explore options for scaling horizontally (adding more servers) or vertically (upgrading existing servers). - Consider redundancy (failover servers) to handle unexpected downtime. 9. CDN (Content Delivery Network): - Use a CDN to distribute static content (images, CSS, JS) globally and reduce load on the backend. 10. Profiling and Debugging: - Profile backend code to identify bottlenecks. - Use tools like New Relic, Xdebug, or FlameGraphs. 11. Communication and Documentation: - Document your findings, steps taken, and solutions. - Communicate transparently with stakeholders, including management, about the issue and progress. 12. Collaborate with Backend Team: - Work closely with backend developers to troubleshoot and resolve issues. - Foster a collaborative environment to find solutions together. Remember that solving backend performance issues is a team effort. Don't hesitate to seek help from colleagues or online communities. Your proactive approach and problem-solving skills will make a difference
@PlusePop8 ай бұрын
@@RaghavPal thanks alot Raghav, i knew i could count on you
@Manojj72579 ай бұрын
Sir can you also make appium with Python series it will really help us Plz sir make it
@RaghavPal9 ай бұрын
I will plan for it Manoj
@Manojj72579 ай бұрын
@@RaghavPal thankyou sir
@pravalikamailaram42698 ай бұрын
Can you please make tutorial videos on how to automate desktop applications using appium in windows/Mac
@RaghavPal8 ай бұрын
I will plan on this Pravalika
@syedmohsinali39066 ай бұрын
It is important to work with TestNG when doing app automation. I am doing with IntelliJ, and Java using Appium, selenium, and Maven. Can you tell me the right way which tools are required..? I am on the right way or not..? refer me to a tutorial that can resolve my queries.
@RaghavPal6 ай бұрын
Syed To confirm, you should have the following tools in your project: * IntelliJ as your IDE * Java as your programming language * Appium for mobile app automation * TestNG for creating and running tests * Maven for managing project dependencies and building your project Remove Selenium: As you're using Appium for mobile app automation, you don't need Selenium in your project. Remove Selenium from your project to avoid any potential conflicts or confusion. Verify your project structure: Make sure your project structure is correct, with the following directories and files: * `src/main/java`: contains your Java test classes * `src/test/java`: contains your TestNG test classes * `pom.xml`: your Maven configuration file * `appium` dependencies in your `pom.xml` file Next steps: 1. Ensure you have the correct Appium dependencies in your `pom.xml` file. 2. Write your TestNG test classes in `src/test/java` and use Appium to automate your mobile app. 3. Use IntelliJ to run your TestNG tests and verify the results. By following these steps, you should be on the right track for app automation with TestNG, IntelliJ, Java, Appium, and Maven -
@syedmohsinali39066 ай бұрын
@@RaghavPal Thanks a lot it's beneficial for me, any video or tutorial you have..? in which a sample project is created using Appium, TestNG, Maven via IntelliJ, and java...
@RaghavPal6 ай бұрын
You can find creating of appium framework in my old appium playlist here - automationstepbystep.com/ but i have used Eclipse
@MindYourbusiness-g7vАй бұрын
Hello sir i hope you're doing well, i face a problem when i run automations tests with appium + robot framework the app closed unexpectadly or doesn'it reconize some element i try everything with no result could you suggest me something plz sir
@RaghavPalАй бұрын
1. *Update Tools* : Ensure Appium, libraries, and Robot Framework are up to date. 2. *Check Logs* : Review Appium and device logs for errors. 3. *Use Stable Locators* : Prefer `resource-id` or `accessibility-id` over XPath 4. *Increase Wait Times* : Use `implicit wait` and `wait for element` commands 5. *Verify Capabilities* : Check `platformName`, `deviceName`, and `automationName` 6. *Switch Contexts* : Switch between `NATIVE_APP` and `WEBVIEW` for hybrid apps 7. *Check Permissions* : Ensure the app has all required permissions 8. *Restart Setup* : Reboot the device/emulator and restart the Appium server 9. *Test App Stability* : Run the app manually to ensure it doesn’t crash 10. *Inspect Elements* : Use Appium Inspector or UiAutomatorViewer for debugging -
@MindYourbusiness-g7vАй бұрын
@@RaghavPal the app even sometimes manually blocked in some element but i dont know how to approve it to my team developement so they could understand that it is something in performance of the app
@RaghavPalАй бұрын
will need to check with your team and check the logs too
@MindYourbusiness-g7vАй бұрын
@@RaghavPal Thank you sir
@Bluefanatic_3 ай бұрын
is this an update to the previous appium playlist? or a continuation?
@RaghavPal3 ай бұрын
This is for Appium 2. You can do the setup part using this playlist if you are using Appium 2. Rest the framework part can be followed from earlier playlst
@Bluefanatic_3 ай бұрын
okay. thanks for all you do
@traptiagarwal91926 ай бұрын
@RaghavPal i need help in installing & integrating eclipse with appium
@RaghavPal6 ай бұрын
Trapti Certainly! Let's get you started with installing and integrating Appium Studio for Eclipse. This lightweight plugin allows you to kick off your Appium testing using real devices directly from Eclipse. Here are the steps: 1. Installation of Appium Studio for Eclipse: - Prerequisites: - Ensure you have Eclipse version 4.6 or higher installed. - Sign up for a SeeTest Digital Assurance Lab account (it provides access to remote devices). - Two Installation Options: - Eclipse Marketplace: 1. Inside Eclipse, go to Help ➡️ Eclipse Marketplace. 2. Search for "Appium Studio" and click Install. 3. Agree to the User Agreement and allow Eclipse to reboot. - Install from File: 1. [Download the Appium Studio for Eclipse installation file] www.softwaretestinghelp.com/appium-studio-for-eclipse-tutorial-12/ 2. In Eclipse, navigate to Help ➡️ Install New Software.... 3. Click Add, then select the downloaded zip file. 4. Choose STAE (SeeTest Automation Eclipse), accept terms, and click Finish. 2. Connecting to Remote Mobile Devices: - Register for the SeeTest Digital Assurance Lab to access real Android and iOS devices. - Generate an access key (username, password, and project name) to connect to the lab. - Develop and execute Appium tests on these devices while monitoring in real time. --
@vishalmunjole6 ай бұрын
HI Raghav, It is really very good content. Is it possible to cover Windows application Automation using Appium2?
@RaghavPal6 ай бұрын
I will plan Vishal
@sairammattaparthi33554 ай бұрын
Which should i watch to learn complete about the Appium The appium 1 or appium 2 (current) Please give me reply
@RaghavPal4 ай бұрын
Sai If you are using the latest Appium i.e. Appium 2 you can watch this series. In this playlist i have covered all the setup part. After the setup if you like to start project. can watch the old series for setting up the project and framework
@devika.c15989 ай бұрын
Sir, please make daily videos on appium.
@RaghavPal9 ай бұрын
I will try my best on this
@akhilrathore6 ай бұрын
Appium Doctor is deprecated since the Appium server v 2.4, is there any alternative.
@RaghavPal6 ай бұрын
Akhil Appium Doctor is still active and can be used with Appium 2.x.x versions.. let me know what is the source of this information
@shyamsundarkadirvelu30838 ай бұрын
Hi Raghav First of all, I would like thank you for posting this video. It would be great, if you could post the second tutorial as well. After going through the video, I was able to upgrade to Appium from 2x from Appium 1x. However, still facing "--allow-cors" issue. I am unable to resolve it even after so many attempts.. Node version: v20.12.2 Npm version: v 10.5.0 Appium : v2.5.3 Is above installation alright or should I downgrade it?. Please let us know. Thanks
@RaghavPal8 ай бұрын
Shyamsundar It looks like you're encountering an issue related to the `--allow-cors` flag in Appium. Let's address this! The `--allow-cors` flag is used to enable Cross-Origin Resource Sharing (CORS) headers in the Appium server. Without this flag, you might face connectivity issues when trying to use Appium Inspector or interact with your app. Here are a couple of steps you can take to resolve this issue: 1. Add the `--allow-cors` Flag: Start your Appium server with the `--allow-cors` flag. You can do this by running the following command in your terminal: ``` appium --allow-cors ``` This instructs the server to send the correct CORS-related headers, making it possible to create a session 2. Check Your Appium Version: Ensure that you're using the same version of Appium globally as well as in your project. Sometimes version mismatches can cause issues. You can check your global Appium version using: ``` appium -version ``` If needed, install the same version of Appium in your project using npm. For example: ``` npm install -g appium@next ``` This should help resolve the problem Remember to restart your Appium server after making any changes. If you encounter this issue with a cloud provider, they might need to apply the fix on their side, as they host the Appium server Give these steps a try, and hopefully, it will resolve the `--allow-cors` issue for you
@shyamsundarkadirvelu30838 ай бұрын
@@RaghavPal Thanks for responding. I read through the following document Link 1: appium.io/docs/en/2.4/quickstart/requirements/ The above document says that Node.js version in the SemVer range ^14.17.0 || ^16.13.0 || >=18.0.0 So I installed node js v18.20.2 & npm v10.5.0. After that i executed the command npm i -g appium. The appium v2.5.4 got installed. Along with this installed Appium-Inspector-windows-2024.3.1-x64 After that, i executed the command appium --allow-cors. & then opened the appium inspector. Still i am facing the following. Error Could not connect to Appium server URL '127.0.0.1:4723/wd/hub'. Please check if the server is running and the URL is correct (valid URLs can be found at the start of the Appium server log). If you are using the Inspector's browser version, ensure the server has been started with '--allow-cors'. I am unable to install the uiautomator 2. Here are my questions, kindly request you to help me with same. What is node js version that we need to install in order to support appium v2.5.4?. What is appium inspector version which we need to install to support v2.5.4 what is the additional drivers that we need to install to support android automation.
@RaghavPal8 ай бұрын
Shyam 1. Node.js Version for Appium v2.5.4: - Appium v2 currently claims support for Node.js versions v14.0.0 and newer. - The project is considering limiting the support for non-"active" Node.js LTS releases (those in "maintenance" mode) to the latest minor version¹ - As of this writing, the latest minor version of the maintenance LTS line is v14.20.0. 2. Appium Inspector Version for Appium v2.5.4: - To use Appium Inspector with Appium v2.5.4, you should download the latest release of Appium Inspector. - As of now, the latest release is v2024.3.4 3. Additional Drivers for Android Automation: - For Android automation, you'll need the UiAutomator2 driver. - UiAutomator2 is a test automation framework for Android devices that automates native, hybrid, and mobile web apps. - It's part of the Appium mobile test automation tool and operates within the scope of the W3C WebDriver protocol. - To add the UiAutomator2 driver to your Appium 2 distribution, use the following command: ``` appium driver install uiautomator2 ``` - Make sure you meet the prerequisites for UiAutomator2, including having the Android SDK Platform tools installed, setting up the Android emulator or real devices, and ensuring the correct Java JDK version¹. Remember to follow the installation steps carefully
@shyamsundarkadirvelu30838 ай бұрын
@@RaghavPal Thank you so much for your time & patience. The issue got resolved.
@a_dark_chocolate8 ай бұрын
I am getting an error when I type npm -v saying that - Error: Cannot find module 'C:\Program Files odejs ode_modules pm\bin ode_modules pm\bin pm-prefix.js' and Error: Cannot find module 'C:\Program Files odejs ode_modules pm\bin ode_modules pm\bin pm-cli.js' What should I do?
@RaghavPal8 ай бұрын
Aishwarya The error message you're encountering indicates that Node.js/npm is having trouble locating certain modules. Let's troubleshoot this issue step by step: 1. Check Node.js Installation: - First, ensure that Node.js is correctly installed on your system. - You can download Node.js from the official website and follow the installation instructions for your operating system. 2. Verify npm Installation: - Open a command prompt or terminal window. - Type `npm -v` and press Enter. - If you see the version number (e.g., "7.24.0"), then npm is installed and accessible from the command line. 3. Check npm Global Installation Path: - The error message suggests that npm is looking for modules in a specific path (`C:\Program Files odejs ode_modules pm\bin ode_modules pm\bin`). - Verify that this path exists on your system. - If not, you may need to reinstall npm globally: - Open a command prompt or terminal as an administrator. - Run the following command to uninstall npm globally: ``` npm uninstall -g npm ``` - Then reinstall npm globally: ``` npm install -g npm ``` 4. Check PATH Environment Variable: - Ensure that the directory containing npm (usually `C:\Program Files odejs`) is added to your system's PATH environment variable. - To check: - Open the System Properties (you can search for it in the Start menu). - Go to the Advanced tab and click on the Environment Variables button. - In the System Variables section, find the Path variable and click Edit. - Add the path to the directory where npm is installed (e.g., `C:\Program Files odejs`) to the list of paths. Separate multiple paths with semicolons. - Click OK to save the changes. - Restart your command prompt or terminal for the changes to take effect. 5. Clear npm Cache: - Sometimes, cached data can cause issues. Try clearing npm's cache: ``` npm cache clean --force ``` 6. Reinstall Node.js and npm: - If none of the above steps work, consider uninstalling Node.js completely and then reinstalling it. - Make sure to remove any remnants of the previous installation.
@a_dark_chocolate8 ай бұрын
@@RaghavPal It worked👍 Thank you so much 😊
@gmbnuts66179 ай бұрын
Hai raghav, is it appium just only can using with java? Cannot using javascript?
@RaghavPal9 ай бұрын
Appium is not limited to Java; you can definitely use JavaScript as well Appium supports multiple programming languages that have Selenium client libraries, including JavaScript with Node.js
@онвыжилпослеаборта7 ай бұрын
good job fren
@RaghavPal7 ай бұрын
Thanks a lot
@lady.stm816 ай бұрын
Thankyou
@RaghavPal6 ай бұрын
Most welcome
@indian_geocacher9 ай бұрын
Hey cannot find the document that you are referring in the description.Can you please comment the link and pin it would be very helpful. Thanks
@RaghavPal9 ай бұрын
Mayank it's added in the descsription tinyurl.com/Appium2-Part-1 Also pinned
@alexanderkomanov41519 ай бұрын
Thanks a lot!!!
@RaghavPal9 ай бұрын
Most welcome Alexander
@Motivation-w7r5 ай бұрын
How to install in Linux ubuntu ?
@RaghavPal5 ай бұрын
To install a package or software in Linux Ubuntu, you can follow these step-by-step instructions: Method 1: Using the Ubuntu Software Center (Graphical Method) 1. Open the Ubuntu Software Center: You can find it in the Applications menu or search for it in the Dash. 2. Search for the package: In the Software Center, type the name of the package you want to install in the search bar. 3. Select the package: From the search results, select the package you want to install. 4. Click the "Install" button: Click the "Install" button to begin the installation process. 5. Authenticate: You may be prompted to enter your administrator password to authenticate the installation. 6. Wait for the installation to complete: The package will be downloaded and installed. You can monitor the progress in the Software Center. Method 2: Using the Command Line (Terminal) 1. Open the Terminal: You can find the Terminal in the Applications menu or press `Ctrl + Alt + T` to open it. 2. Update the package list: Run the command `sudo apt update` to update the package list. 3. Install the package: Run the command `sudo apt install ` replacing `` with the actual name of the package you want to install. 4. Authenticate: You may be prompted to enter your administrator password to authenticate the installation. 5. Wait for the installation to complete: The package will be downloaded and installed. You can monitor the progress in the Terminal. Method 3: Using a.deb file (Offline Installation) 1. Download the.deb file: Download the `.deb` file for the package you want to install from a trusted source. 2. Open the Terminal: You can find the Terminal in the Applications menu or press `Ctrl + Alt + T` to open it. 3. Navigate to the download location: Use the `cd` command to navigate to the directory where you downloaded the `.deb` file. 4. Install the package: Run the command `sudo dpkg -i .deb` replacing `` with the actual name of the package. 5. Authenticate: You may be prompted to enter your administrator password to authenticate the installation. 6. Wait for the installation to complete: The package will be installed. You can monitor the progress in the Terminal. That's it! Your package should now be installed on your Ubuntu system -
@nitinjawale16248 ай бұрын
video sound is low sir
@RaghavPal8 ай бұрын
Yes Nitin, a little low, with high sound it was taking some background noises.. so i adjusted to optimum level. Can keep your system or video player volume to high and if needed can use headphones..
@nitinjawale16248 ай бұрын
@@RaghavPal Sure sir
@vishwajitjadhav51799 ай бұрын
❤️❤️
@RaghavPal9 ай бұрын
Thanks Vishwajit
@shyamsundarkadirvelu30838 ай бұрын
Unable to install uiautomator2 × Installing 'uiautomator2' using NPM install spec 'appium-uiautomator2-driver' Error: × Encountered an error when installing package: npm command 'install --save-dev --no-progress --no-audit --omit=peer --save-exact --global-style --no-package-lock appium-uiautomator2-driver --json' failed with code 1. STDOUT: { "error": { "code": 1, "summary": "command failed", "detail": "C:\WINDOWS\system32\cmd.exe /d /s /c node install-npm.js [15:08:34] Error installing Chromedriver: unable to verify the first certificate [15:08:35] Error: unable to verify the first certificate at Function.AxiosError.from (C:\Users\Healthcubed\.appium ode_modules\appium-uiautomator2-driver ode_modules\axios\lib\core\AxiosError.js:89:14) at RedirectableRequest.handleRequestError (C:\Users\Healthcubed\.appium ode_modules\appium-uiautomator2-driver ode_modules\axios\lib\adapters\http.js:610:25) at RedirectableRequest.emit (node:events:529:35) at ClientRequest.eventHandlers. (C:\Users\Healthcubed\.appium ode_modules\appium-uiautomator2-driver ode_modules\follow-redirects\index.js:38:24) at ClientRequest.emit (node:events:517:28) at TLSSocket.socketErrorListener (node:_http_client:501:9) at TLSSocket.emit (node:events:517:28) at emitErrorNT (node:internal/streams/destroy:151:8) at emitErrorCloseNT (node:internal/streams/destroy:116:3) at processTicksAndRejections (node:internal/process/task_queues:82:21) at Axios.request (C:\Users\Healthcubed\.appium ode_modules\appium-uiautomator2-driver ode_modules\axios\lib\core\Axios.js:45:41) at processTicksAndRejections (node:internal/process/task_queues:95:5) at retrieveData (C:\Users\Healthcubed\.appium ode_modules\appium-uiautomator2-driver ode_modules\appium-chromedriver\lib\utils.js:92:5) [15:08:35] Downloading Chromedriver can be skipped by setting the'APPIUM_SKIP_CHROMEDRIVER_INSTALL' environment variable." } }
@RaghavPal8 ай бұрын
Shyam The error message indicates a problem related to verifying certificates and downloading Chromedriver. Let's explore some solutions: 1. Certificate Verification Issue: - The error message mentions "unable to verify the first certificate." This could be due to network or security settings. - Try running the installation command with the environment variable `APPIUM_SKIP_CHROMEDRIVER_INSTALL=1`: ``` APPIUM_SKIP_CHROMEDRIVER_INSTALL=1 appium driver install uiautomator2 ``` - This skips the Chromedriver installation, which might resolve the certificate issue³. 2. Chromedriver Installation: - If you need Chromedriver for webview automation, ensure that it's installed correctly. - You can manually install Chromedriver using: ``` npm install -g appium-chromedriver ``` - Then retry installing the uiautomator2 driver. 3. Node Modules Cleanup: - Sometimes conflicts arise from existing node modules. - Delete the contents of the `node_modules` folder at the path `/Users/amir/.appium/node_modules`. - After cleaning up, try installing the uiautomator2 driver again². 4. Update Node and NPM: - Ensure you're using an updated version of Node.js and npm. - Update npm using: ``` npm install -g npm@latest ``` - Then retry the installation command. Remember to check your network connectivity and security settings.
@shyamsundarkadirvelu30838 ай бұрын
@@RaghavPal Thank you so much time and patience, the issue finally got resolved...
@paulovitordasilvasantos64793 ай бұрын
Hello 1st of all thanks for your videos Im had the warning after installed appium in my PC npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated glob@6.0.4: Glob versions prior to v9 are no longer supported npm warn deprecated rimraf@2.4.5: Rimraf versions prior to v4 are no longer supported is this critical?
@RaghavPal3 ай бұрын
Paulo Those warnings you're seeing after installing Appium aren't a big deal. They just mean some of the parts Appium uses are a bit old and might get replaced later. Should you worry? Not right now: Appium should still work fine Maybe in the future: If Appium gets a big update, you might need to reinstall it later What to do: Ignore it for now: If everything's working, don't sweat it Stay updated: Keep an eye out for Appium updates, just in case. Basically, those warnings are like a heads-up, not a red alert. You're good to go with Appium for now -
@MadhuriAdaskar-n3k5 ай бұрын
Hi sir, please help i am installing appium using cmd command npm install -g appium i am getting this error npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated rimraf@2.4.5: Rimraf versions prior to v4 are no longer supported npm warn deprecated glob@6.0.4: Glob versions prior to v9 are no longer supported changed 431 packages in 31s 57 packages are looking for funding run `npm fund` for details
@RaghavPal5 ай бұрын
Madhuri Let's tackle this step by step. The warnings you're seeing are related to deprecated packages, which means they are no longer supported but should not prevent Appium from being installed. However, if you're facing issues, here are some steps to resolve them: ### Step 1: Update Node.js and npm Ensure you have the latest versions of Node.js and npm. You can update them using the following commands: ```sh npm install -g npm ``` For Node.js, download the latest version from the [official website](nodejs.org/). ### Step 2: Clean npm Cache Sometimes, clearing the npm cache can resolve installation issues: ```sh npm cache clean --force ``` ### Step 3: Install Appium with Force Flag Try installing Appium with the `--force` flag to overwrite any existing files that might be causing issues: ```sh npm install -g --force appium ``` ### Step 4: Check Permissions If you're on a Unix-based system (like macOS or Linux), you might need to use `sudo` to install globally: ```sh sudo npm install -g appium --unsafe-perm=true --allow-root ``` ### Step 5: Verify Installation After installation, verify that Appium is installed correctly by running: ```sh appium -v ``` ### Step 6: Address Specific Warnings The warnings about deprecated packages can be addressed by updating those packages if necessary. However, they should not prevent Appium from functioning. -