Selenium’s Post

Today marks the beginning of my journey with Cypress! While many experts tout the ease of installing Cypress compared to Selenium, my initial experience was quite challenging. Encountering an "access denied" error when running npm commands in VSCode's PowerShell was a significant hurdle. After diving into Stack Overflow and conducting some research, I finally managed to open Node.js through VSCode. In the attached photo, you can see I'm in the process of configuring Cypress for E2E testing on my device's Chrome browser. Although Cypress defaults to the Electron browser, I'm excited to explore its capabilities with Chrome. This is just the start of my exploration with Cypress for automation testing. Stay tuned for updates on my LinkedIn profile as I share more insights and progress. #Cypress #AutomationTesting #E2ETesting #Selenium #NodeJS #VSCode #TechJourney #LearningAndDevelopment

Last week, the 2023 State of JS Awards was announced and Jason Huggins made a post about the success of Selenium (posted in the comments). Lately, I've been thinking a lot about what it means to be a successful open source project -- in fact, in my weekly X Spaces that's usually a question I ask the maintainers. Everyone's going to define success differently, but each industry has an implied standard of success. We see this when we look at the most popular or talked about people or projects, but the reality is that these projects and people aren't necessarily the most successful. They might be the most vocal or controversial. (The irony isn't lost on me that recently I thought to myself, "Well, I only have a ~year to make a 40 under 40 list.) Recognition doesn't mean #success. But if that's the case, how do we understand if our projects are successful? How do we better define #standards that allows for recognition of people and projects that deserve it in #opensource and elsewhere?

We, software engineers, are all familiar with grinding Leetcode. Today, I want to share that I created a Chrome extension for myself to quickly open a new tab with a random Neetcode-150 problem in a single key/click. Here is what I learned from this simple project: 1. Selenium - Headless Browser Automation To be honest, I could have just searched some websites that have problem lists on their websites and web-scraped directly by reading the HTTP Response. However, I was looking at the original website (https://neetcode.io) and learned that I couldn't directly web-scrape the problem list and that I needed to click a few buttons to see the problem list. When you face a problem, you find a solution. So, I looked around how to perform browser automation: I want my code to click buttons on the website instead of me. After seeing choices like Selenium, and Puppeteer, I chose Selenium. The documentation and tutorials are clear enough that I could learn it in a few minutes and successfully get the Neetcode 150 from neetcode.io. Another small hurdle is that the problem list contains some paid problems (I don't really want to pay Leetcode Premium at the moment). I got around this by web-scraping the premium problem list from https://leetcode.com and filtering the premium problems out of my list. 2. Chrome Extension After looking around the documentation by Chrome, creating an extension requires regular skills you need to create a website plus a manifest file. I only need a simple extension that randomly chooses one problem from my problem list and opens a new tab for it. I quickly spin up and add the extension to my Brave browser. Since Brave is based on the Chromium web browser, it has no problem accessing Chrome extensions. The whole day was such a fun day since I just learned a lot: Selenium for browser automation and Chrome extension development to create an extension. I just wanted to share this joy with you guys. #selenium #chromeextension #browserautomation #webscraping

I've recently implemented end-to-end testing in my React application using Cypress and set up a GitHub Actions workflow to automatically run the tests on every commit. It’s been great to see how Cypress supports a user-like and programmatic approach, similar to React Testing Library, which I had previously worked with. I also enjoyed learning how to deploy a self-hosted actions runner during the implementation process, greatly improving my continuous integration environment. #cypress #github #reactjs #frontend #react #devops #continuousintegration #automationtests

🚀 I developed an automation framework using SeleniumJava, TestNG, Commons-IO, and ExtentReports to navigate Amazon's website from login to checkout page. 🛒💻 Whenever a test fails, ExtentReports captures the error and provides visual proof with screenshots. #Automation #TestNG #Selenium #ExtentReports 

Docker images for Selenium Grid support dynamic grid! Don't know why the feature is not covered in Selenium docs, but it supports on-demand creation and termination of browser containers in Docker and Kubernetes. It basically replaces Selenoid and Moon! See the repo README to know more https://lnkd.in/d3vhGjri Not sure, what surprises me more: the feature or the fact, that it's not mentioned on the Selenium website. #selenium #docker #kubernetes

Hello Folks, Hope everyone is doing good. I wrote a blog that talks about how to integrate WebDriverIO Appium tests with BrowserStack and implement CICD via GitHub Actions. Feel free to give it a read if you find it interesting. Thank you. #automationtesting #softwaretesting #qaautomation #qa #webdriverio #browserstack #appium #githubactions #blogpost

Struggling to harness the full potential of the free version of Cypress in parallel on Jenkins? Your solution is here! 💻 Check out my blog post at Yugabyte and discover expert insights to optimize web testing using parallel Cypress with Docker, Jenkins, and the revolutionary Mochawsome framework. 💡🛠️ 🔍 Master the art of streamlined testing with the free version of Cypress, while seamlessly pushing reports to Report Portal and leveraging the power of Mochawesome for enhanced insights. 🚀 Elevate your testing efficiency with proven techniques, optimizing every step of the process. #WebTesting #TestAutomation #Cypress #Docker #Jenkins #ReportPortal #mochawesome

I take advantage of the weekends to continue working on my personal projects and to keep learning and refreshing my knowledge of new technologies. On this occasion, I completed a temperature-seeking application using #React, #TypeScript, #CSSModules and an external #API. I also used #Valibot to validate queries when using TypeScript with the API (it seems TypeScript can be a bit tricky when working with external APIs ). For my next project, I'll be using another external API and exploring #Zod, which is similar to Valibot. https://lnkd.in/dnthXNH5

🚀 Excited to share the final chapter of my Cypress Project Series! 🧪🔍🌐 In this series, we delved into advanced automated web testing with Cypress. 🌟 Let's recap some of the cool features we explored: 1. Retrying Failed Tests: We configured retry attempts for both `cypress run` and `cypress open` modes, enhancing the stability of test execution. Much smoother than dealing with retries in Selenium! 2. Cross-Browser Testing: With Cypress, running tests across different browsers is a breeze. Just use the `--browser` flag to specify the browser, and you're good to go. No more lengthy setup like in Selenium. 3. Headless Mode Execution: Speed up test execution using the `--headless` flag. Perfect for integrating with your CI/CD pipelines. Say goodbye to cumbersome headless mode configuration in Selenium. 4. Parallel Execution (Cypress Cloud): Cypress Cloud offers parallel execution for blazing-fast testing. Use the `--parallel` flag to harness this power. No need to set up complex grids as in Selenium. Check out the complete series on my [LinkedIn Learning profile](https://lnkd.in/gfA-bZwD), and the source code on [GitHub](https://lnkd.in/g3AWYhfd) to explore these features in action! Don't forget to stay curious and keep learning. 🌐🔥 #CypressProject #AutomationTesting #WebTesting #QualityAssurance #TestAutomation #CypressVsSelenium --- Looking to enable these features in Selenium? It's certainly possible, but you'll need to juggle with more configurations and dependencies. Cypress simplifies the process, allowing you to focus on what matters most – writing robust tests! 💪 #cypress #unittesting #automatedtesting #webautomation #testautomation #webdevelopment #cypresstest #learning #webautomation #seleniumcomparision #testautomation #node #nodejs #javascript #nodejsdeveloper #sdet #seleniumautomation #selenium #seleniumtesting