4 ms·

I 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 p

I 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?

neerajdotname2 9y ago
We at http://www.trinityradar.com/ 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.
- albertgoeswoof 9y ago
  Chrome is the new IE
  - reitanqild 9y ago
    In case anyone wonders, here are some points to get you started: [X] created by a company that can't be trusted [X] made mandatory by lazy devs && corporate bean counters who refuse to let other developers do the professional thing and make stuff work cross platform [X] worse than the alternatives in many ways except being feature-by-feature and bug-by-bug compatible with the market leaders (yep: memory use, battery use, extensions)
- chinathrow 9y ago
  Your site says "Run tests in Chrome, Firefox, or in IE 11" - so is that claim still true or am I missing something?
  - neerajdotname2 9y ago
    We need to update homepage along with all screenshots since all screenshots with Firefox are outdated now.
- Vinnl 9y ago
  But that has nothing to do with the IDE no longer being available, but merely as a cost-saver for you guys (I presume).
simonstewart 9y ago
We knew this was coming down the track, but the selenium project lacked the people to prevent it from happening. Sauce Labs donated Selenium Builder (nee Sauce Builder) to the project to try and help. Applitools have recently leant some engineering muscle to the problem. The problem breaks down into two main areas: * Technical: the underpinnings have switched from the XPI model to Web Components. Mozilla are doing what they think is best for their browser, and I know that they make their choices with thought and data. * People: every successful OSS project has a company or person acting as its champion. The selenium project has people working flat out for the language bindings, the w3c "WebDriver" spec, grid, and supporting the community. We lack a champion with the time to spend on IDE. We can fix the technical side of things. The thing that we could really do help with is the people-side....
- hardwaresofton 9y ago
  Thanks for the response! Always curious how moves like this help people who are actually doing stuff in the browser automation/testing scene (I am just a trend follower/leech off the work being done), glad to hear you guys were ready and props on thinking ahead.
Vinnl 9y ago
Note that SauceLabs, Browserstack etc. will continue to work. This was just an extension that allowed you to create tests by click through your website rather than writing them by hand. Resulted in far brittler tests, but useful to some apparently.

I 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?

neerajdotname2 9y ago

We at http://www.trinityradar.com/ 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.

albertgoeswoof 9y ago
Chrome is the new IE
- reitanqild 9y ago
  In case anyone wonders, here are some points to get you started: [X] created by a company that can't be trusted [X] made mandatory by lazy devs && corporate bean counters who refuse to let other developers do the professional thing and make stuff work cross platform [X] worse than the alternatives in many ways except being feature-by-feature and bug-by-bug compatible with the market leaders (yep: memory use, battery use, extensions)
chinathrow 9y ago
Your site says "Run tests in Chrome, Firefox, or in IE 11" - so is that claim still true or am I missing something?
- neerajdotname2 9y ago
  We need to update homepage along with all screenshots since all screenshots with Firefox are outdated now.
Vinnl 9y ago
But that has nothing to do with the IDE no longer being available, but merely as a cost-saver for you guys (I presume).

simonstewart 9y ago

We knew this was coming down the track, but the selenium project lacked the people to prevent it from happening. Sauce Labs donated Selenium Builder (nee Sauce Builder) to the project to try and help. Applitools have recently leant some engineering muscle to the problem. The problem breaks down into two main areas: * Technical: the underpinnings have switched from the XPI model to Web Components. Mozilla are doing what they think is best for their browser, and I know that they make their choices with thought and data. * People: every successful OSS project has a company or person acting as its champion. The selenium project has people working flat out for the language bindings, the w3c "WebDriver" spec, grid, and supporting the community. We lack a champion with the time to spend on IDE. We can fix the technical side of things. The thing that we could really do help with is the people-side....

hardwaresofton 9y ago
Thanks for the response! Always curious how moves like this help people who are actually doing stuff in the browser automation/testing scene (I am just a trend follower/leech off the work being done), glad to hear you guys were ready and props on thinking ahead.

Vinnl 9y ago

Note that SauceLabs, Browserstack etc. will continue to work. This was just an extension that allowed you to create tests by click through your website rather than writing them by hand. Resulted in far brittler tests, but useful to some apparently.