Comments for Blargon7

Comment on Test day + Meetup = Success! by Dave

Dave — Fri, 24 Feb 2012 22:09:16 +0000

Thanks for your comment, Suchitra! Unfortunately there are no slides or presentations to share. The meetup event was highly interactive and any demos were done over-the-shoulder. We hope to repeat the event, and hopefully can vary the location in the future.

Comment on Test day + Meetup = Success! by suchitra

suchitra — Fri, 24 Feb 2012 20:24:41 +0000

could you please provide some slides/presentations of the discussions? san francisco is way too far for me and hence cannot make it there.

thanks
suchitra

Comment on Automating BrowserID with Selenium by Dave

Dave — Wed, 08 Feb 2012 13:38:32 +0000

We've raised an enhancement request against BrowserID to give us a way to create users via an API. This would allow tests to create suitable users as part of their setup. Of course, there would likely also be a need for the application under test to have a similar API.

Comment on Automating BrowserID with Selenium by dwh

dwh — Wed, 08 Feb 2012 02:19:26 +0000

It strikes me that the really awkward/useful/fiddle bit of library code would be the piece which lets you use or create test users… Is there a common bit of code for saying “I want a user that exists/doesn’t exist/does or doesn’t have this password?

Comment on Automating BrowserID with Selenium by A Smattering of Selenium #80 « Official Selenium Blog

A Smattering of Selenium #80 « Official Selenium Blog — Wed, 08 Feb 2012 01:07:23 +0000

[...] Automating BrowserID with Selenium is pretty awesome. (As is BrowserID.) Now if this was only installable via pip or easy_install… [...]

Comment on Hooking Android up to the (Selenium) Grid by stackedsax

stackedsax — Wed, 11 Jan 2012 02:16:33 +0000

flynnid is what I’m using, yes. It threw some error with python 3.2, but was fine with 2.7.

I’ll try setting remoteHost in the json file and see if will work. Thanks for the suggestion.

Comment on Hooking Android up to the (Selenium) Grid by Dave

Dave — Tue, 10 Jan 2012 10:48:20 +0000

Hey stackedsax,

Good point. I’m sure I had this running locally, although I can’t see an obvious way around your issue. You could try starting an additional node with only the Android capability, and set the remoteHost property to match the actual host/port of the Android device/emulator. I believe this is what is sent to the hub when registering a node, and although it usually reflects the host/port properties for the node you should be able to override it.

Also, have you tried using FlynnID?

Cheers,
Dave

Comment on Hooking Android up to the (Selenium) Grid by stackedsax

stackedsax — Tue, 10 Jan 2012 07:05:42 +0000

Thanks for this info — I got the android emulator registered on the grid thanks to your flynnid python script.

I had one question about a comment you make here, though. Are you sure this is quick and easy:

The quick solution would have been to just start a Selenium server with the details for the Android node.

You want to tell grid where the android emulator is running, and the port is part of that equation. As far as I can see, if you start the selenium server and set the port parameter, it will also run on that exact same port. So there will be a conflict between the emulator running on port 8081 and the selenium server you’re trying to start on port 8081.

This is what I ran into before I started asking over in the IRC channel, and I just want to see if I’m missing something totally obvious.

The fix, it seems to me, would be to have the selenium server allow ports per browser definition. I tried setting port per browser, but it didn’t seem to change anything. I didn’t dive into the code to see if it should or shouldn’t work, but since it failed and there’s no mention of that feature anywhere I assumed it’s not actually a feature.

Here’s an example of what I’m describing:

https://gist.github.com/1587576

Comment on Introducing Firefox Endurance Testing by cioara

cioara — Sun, 08 Jan 2012 13:31:06 +0000

I didn’t knew about Telemetry, thank you very much for clearing this up for me. Now my first request does not make any sense.

Comment on Introducing Firefox Endurance Testing by Dave

Dave — Fri, 16 Dec 2011 12:10:39 +0000

I'm interested to know what additional information you would suggest we gather? Were you aware of Telemetry? It's been available since Firefox 7 and allows users to opt-in to sending anonymous performance related data back to Mozilla.