Asad Ali

How To Install Google Chrome, Selenium & Chromedriver For AWS EC2 Instances

If you’re looking to use selenium and headless browsers on amazon web services (AWS) its essential that you install the relevant versions of selenium, ChromeDriver and Google Chrome to your EC2 instance. In this guide you’ll learn how to easily deploy and test a fully functional selenium python environment. Install ChromeDriver You will need to install ChromeDriver which allows you programmatic access to google chrome via the Webdriver API protocol. Go to Google Chrome for Testing GitHub Downloads page: Choose your desired Channel. I am choosing the Stable channel. Copy the URL for chromedriver binary according to your platform. Make sure its HTTP status is 200. I am choosing this URL for my Linux machine: cd /tmp/ wget unzip cd chromedriver-linux64 sudo mv chromedriver /usr/bin/chromedriver chromedriver –version If you get the fallowing error when running ‘chromedriver –version’ it indicates that the shared library file is missing or cannot be found on your system. is a part of the Network Security Services (NSS) library, which is used by various applications for SSL/TLS support. To resolve this issue, you can try the following steps based on your operating system: For Ubuntu/Debian-based systems: For CentOS/RHEL-based systems: Once you’ve installed the required library, try running chromedriver –version again. If the issue persists, you may need to check if there are any other missing dependencies or if there are specific compatibility issues with your system. Additionally, make sure that your system is up-to-date with the latest updates and patches. Install Chrome on Ubuntu, Debian, and Linux Mint Open SSH terminal and use the following commands to install Google Chrome on Debian based Linux distributions, such as Ubuntu, Debian, Kali, and Linux Mint. cd /tmp/ wget sudo apt install ./google-chrome-stable_current_amd64.deb google-chrome –version Running a selinum test: python3 When i try to run the selenium test, I get this error: The error message “ModuleNotFoundError: No module named ‘selenium’” indicates that Python cannot find the Selenium module in your current environment. To resolve this issue, you need to install the Selenium package. You can install Selenium using a package manager like pip. Open a terminal or command prompt and run the following command: pip install selenium Now I get following error: Then I tried running: python3 -m pip install selenium and got the following error: The error “No module named pip” indicates that the pip tool is not installed or not available for your Python installation. In some systems, the python3 installation may not include pip by default. You can install it separately. Here are some general steps: For Debian/Ubuntu-based systems: sudo apt updatesudo apt install python3-pip After this now you need to install selenium module. Using: pip3 install selenium

How To Install Google Chrome, Selenium & Chromedriver For AWS EC2 Instances Read More »

From CVS to Git – A Journey Through Time

Introduction: Explore the fascinating journey of version control systems, from their humble beginnings to the modern era of Git. Discover how these systems have shaped software development, ensuring a seamless track of changes in code and who made them. In the fast-paced world of technology, understanding the roots of version control is crucial. Let’s embark on this insightful journey. From Inception to Revolution: The Birth of Version Control As software development burgeoned, the need to track code changes arose. Version control systems came into existence as early as the 1980s, preceding the era of the internet. The Concurrent Versions System (CVS), created by Walter F. Tichy at Purdue University in 1986, marked a significant milestone. It stored vital information about files, their modifications, and more. However, CVS was not without its flaws, lacking integrity checks and support for binary files. The Rise of Subversion (SVN) CollabNet’s Subversion (SVN) emerged in 2000, addressing CVS’s limitations. With integrity checks and improved binary file support, SVN gained popularity in the open-source community. Yet, it adhered to a centralized VCS model, causing development hiccups when servers were slow or down. Enter the Era of Distributed Version Control In 2005, two game-changing projects initiated the era of distributed version control: Mercurial and Git. The catalyst behind these projects was a controversy involving BitKeeper, a proprietary VCS used by the Linux kernel. After BitKeeper revoked its free license in 2005, Mercurial and Git emerged. Mercurial: High-Performance and Easy Transition Developed by Olivia Mackall, Mercurial offered a high-performance distributed VCS. Its seamless transition for Subversion users and hosting provider support made it a favorite choice. Git: The Linux Kernel’s Solution Linus Torvalds created Git to host the Linux kernel’s source code. Git’s distributed VCS design and free hosting on Github cemented its popularity in the open-source community and beyond. The evolution of version control systems has been an incredible journey. From CVS to Git, these systems have played a vital role in shaping software development. As you explore the world of version control, remember the pioneers like CVS and the innovations like Git that have made code management more efficient than ever. With over two decades of experience, we are excited to see how version control will continue to evolve and empower developers worldwide. Focus Key Phrases: Version control, CVS, Git, software development, code management, history of version control, evolution of version control.

From CVS to Git – A Journey Through Time Read More »