Okay, here’s my blog post about the “lita and edge break up” situation, written in the style of a personal, informal blog:
So, I’ve been messing around with Selenium and, you know, trying to automate some browser stuff. I was using Lita, this Ruby gem, with Edge, and it was okay for a bit. But, man, did things get messy fast.
First, I downloaded the Lita gem. Easy enough, right? Just a simple gem install lita in the terminal. Then, I grabbed the Microsoft Edge WebDriver. You gotta make sure you get the right version for your Edge browser, or things will go south real quick. I found mine by checking the “About Microsoft Edge” section in the browser settings.
Then came the coding. I whipped up a basic Ruby script. It was supposed to be simple: open Edge, go to a website, and… well, that’s where the problems started.
The Trouble Begins
-
The first hiccup? Edge kept crashing. Like, constantly. I’d run the script, and poof, the browser window would just disappear. No error message, nothing. Super frustrating.
-
Even when it did work, it was slow. Like, watching-paint-dry slow. I tried different things, tweaking the code, checking my internet connection (which was fine, by the way), but nothing seemed to help.
-
And the debugging? Forget about it. I spent hours trying to figure out what was going wrong, sifting through documentation and Stack Overflow posts. It felt like I was chasing ghosts.
The Break-Up
I get it, Edge and these third party automation tools, is a pain.
So, yeah, I gave up on Lita and Edge. It just wasn’t worth the headache. I switched over to using Chrome and its WebDriver, and things have been much smoother. I mean, it’s not perfect, there are still occasional glitches, but it’s a world of difference.
I successfully achieved my initial test goal.
My takeaway? Sometimes, the tools just don’t play nice together. Don’t be afraid to try something different if things aren’t working. It might save you a lot of time and frustration in the long run.
