For this exact reason I made an extension for chrome that covers some of it's features: https://chrome.google.com/webstore/detail/e2e-test-builder/p... I'd rather tag elements of interest and record (and adjust manually) than write everything in code.
Firefox 55 and Selenium IDE
41–50 of 132 posts
Re: Firefox 55 and Selenium IDE
#42Re: Firefox 55 and Selenium IDE
#43Of course, Selenium (WebDriver) still works. However, this might be the push for people to investigate other test frameworks. I found TestCafe by DevExpress ( https://devexpress.github.io/testcafe/ ) is a great tool and is also completely open source (MIT!). It's a shame that the community is so small because it's so powerful. Maybe this might be the push that moves some more people over?
Re: Firefox 55 and Selenium IDE
#44I wonder if there's anyone here from SauceLabs or or any other company that does browser automation as a service -- was this easy to see coming? Is everything pants-on-fire there at the moment?
We at http://www.trinityradar.com/ provide browser automation service. We stopped working with Firefox a few months ago since less and less people are using firefox now. We run chrome browser on cloud. Full disclosure: I work for Trinity Radar.
Re: Firefox 55 and Selenium IDE
#45Test recorders are an antipattern. They lure you with their "no programming required!" siren call, but the generated scripts invaribly end up as a fragile, poorly abstracted mess. GUI tests suites, especially those created with recorders, are prone to become unmaintainable beasts full of flaky tests. This old interview with Bret Pettichord makes good points about the use of recorders: https://youtu.be/s_CUPs6xAWw?t=5…
All you said is true, but this doesn't stop Selenium IDE of being a valuable tool. You just need to know when to use it. Without it a lot systems in my company would have zero tests. Not even bad and fragile ones.
When exactly is that ? Never ? That clusterfuck of generated code is useless.
Re: Firefox 55 and Selenium IDE
#46Selenium IDE is a tremendous help for projects that want integration testing, and want to enable any team member to write ballpark tests. Selenium IDE saved us hundreds or thousands of hours. For example, my team took an existing web app with no tests, and had the project manager and junior business analysis go through the entire app with the Selenium IDE, writing tests. This enabled our dev team to start coding fast…
Re: Firefox 55 and Selenium IDE
#47Earlier quoted context omitted.
Are they? The old system is holding improvements back. If they move to a superset of Chrome's they can still get Chrome add-ons and then some. If people value the old extension system that much, then it will live on in one of the FF forks. Regardless Firefox will finally get faster, more responsive, more secure, AND still have a better extension API than Blink/WebKit.
>If people value the old extension system that much, then it will live on in one of the FF forks. Using a fork is also bonkers. I don't trust the security of my web browsing on a fork. Most people won't, either. So Firefox will just get this nice metric saying "most people have not moved to a fork" and will be able to pat themselves in the back. But it's bogus.
Re: Firefox 55 and Selenium IDE
#48Earlier quoted context omitted.
Only reason? I use Firefox because it's way faster, more stable, and from an organization that I trust. I run Nightly, which means that I made the shift to Webextensions last week. My only extension that didn't have a WE version or alternative was LastPass. No surprise, since they seem to take such poor care of their extensions anyway. That's a Deal Breaker for me, so I switched to pass.
Firefox is way faster than what? IE6?
Re: Firefox 55 and Selenium IDE
#49Is there like a electron for firefox xul? There is actually is https://developer.mozilla.org/en-US/docs/Archive/Mozilla/XUL... edit: answering my own question.
Re: Firefox 55 and Selenium IDE
#50Selenium IDE is a tremendous help for projects that want integration testing, and want to enable any team member to write ballpark tests. Selenium IDE saved us hundreds or thousands of hours. For example, my team took an existing web app with no tests, and had the project manager and junior business analysis go through the entire app with the Selenium IDE, writing tests. This enabled our dev team to start coding fast…
If you say that "Selenium IDE saved us hundreds or thousands of hours", why not convince your company to donate 10% of the money saved back to Selenium, so that they maybe have the resources to actually pay someone to continue development of these useful tools?