Selenium Blog

Let’s put Selenium IDE on Firefox 4 is Available for Testing! Now! outside of the normal list. We have a ‘working’ version of Se-IDE for FF4, but don’t really have too too much faith in it (or at least I don’t). Please help test it.

• Eight Techniques to Improve Your Tests is focused on unit tests, but I’m sure something can be gained from them
• Runners are great fun. How the play framework test runner works is therefor also great fun.
• Manage your EC2 instances in your Grid with rubber; a plugin for capistrano
• Some post SeConf blogs are starting to appear
  • Michael Larsen’s Day One, Day Two, Day Three
  • Andy Tinkham mindmapped it
• While not related directly to automation The writing process mimics the script creation process; at least for me.
• AffirmIt! is an April Fool’s joke (I think!) but still good anyways.
• Selenium Fury is a Page Object factory for Ruby.
• It is always important to remember the Bugs that automated tests aren’t good at finding
• Care about using Twist with either the Android or IOS WebDriver APIs? Configuring Twist for Selenium 2 could make you happy then.
• Logs Are Streams, Not Files is an interesting notion to remember.
• All the talks from CukeUp! are online. Because I need to have even more things to not to have time to watch.
• Selenium Commands & Locators Explained is the next in Dave Hunt’s guest series at the Software Testing Club. Pay extra attention to the last sentence of the Link section
• Spynner is a stateful programmatic web browser module for Python with Javascript/AJAX support based upon the QtWebKit framework
• Bring out your dead! applies just as much to Selenium as it does Python.
• No idea how I found design of selenium tests for asp net seems pretty useful. Or at least from the table of contents.
• The Java technology zone technical podcast series has a pretty current podcast with Jason Huggins and Simon Stewart that deals with upgrades, etc.
• XPath, CSS, DOM and Selenium: The Rosetta Stone — given we spent all week last week harping on using CSS instead of XPath, this is a win.
• An excellent reminder that it is not always just the raw number that you need to understand, but the story of the number can be found in Why you can’t compare cross browser execution times of Selenium Tests

Share this:

A Smattering of Selenium #45

So of course by now everyone has seen Selenium 2.0b3: The Next Gen Browser Release and upgraded their rigs. Expect Selenium IDE at some point in the next week with support for FF4 — if you just. can’t. wait. then you could try the bleeding edge for yourself. Logging any bugs you find; of course.

Oh, and there is the whole Selenium Conference next week.

But aside from that, here are the things I have collected.

• headless dotnet browser testing with selenium2 using Jenkins and NSSM (the Non-Sucking Service Manager)
• Frameworks are evil includes this gem: The problem comes when you are blindly following what a framework gives you and you forget your better design skills (like OO or functional skills) to just follow blindly recipes from a given framework.. Exactly.
• Testing jQuery Autocomplete using Capybara or more accurately Using Selenium + Capybara + jQuery to select an option from an AutoComplete
• If you are wrapping your scripts in Cucumber or RobotFramework (or similar), then you owe it to your team to read Putting Cucumber where it’s not supposed to go will hurt!. Especially the 4th adn 5th paragraphs.
• Not new, but FEST appears to open up the Applet space to Se. Not that Applets are really in use much these days. I could have used this in 2007 though.
• Alfajor seems to be a python based metaframework supporting Windmill, WebDriver and a few others.
• Crawljax is an AJAX capable web crawler
• Wait with WaitForCondition discusses some advanced synchronization tricks
• Capybara (and Selenium) with RSpec & Rails 3: quick tutorial is a quick tutorial
• lettuce_webdriver is, naturally, the Python port of Cucumber
• An Update on Our Selenium-Automated AMO Tests (and Automation in General) — AMO is addons.mozilla.org for the acronym impaired.
• A website appears before you! Adventures of a clicky thing is not Se, but still interesting.
• Desafios com o Selenium IDE is in Portuguese, but from what I understand he is trying to build a koans style site for Se-IDE.
• From PyCon is API Design anti-patterns and API Design: Lessons Learned
• Exceptional Ruby Notes has some links to how ruby actually handles exceptions
• Parallelism is not concurrency — in case you were wondering
• Se committer and IE WebDriver re-writer Jim Evans was on Hanselminutes
• Vision Test for ZTL shows how they do image comparison.
• and do does github!
• Selenium Test Day with Mozilla WebQA is TOMORROW – join in to learn / share some tricks with Mozilla
• An Introduction To Selenium IDE is the first in a series of articles that I might not normally link to but I read drafts of and know where they are heading. Either that or I am completely confused
• Step Away from the Tools is an important reminder for those who tend to live in their tools.
• Selenium IDE plugin for the Play! framework
• How the Comodo certificate fraud calls CA trust into question is interesting in itself, but also has a nice explanation of how SSL works. Again, if you are not using certificate-based authentication in your scripts, you do not need SSL turned on outside of production, but should you persist then you should understand what is happening.
• Without stabilisers – why writing your own test harnesses really is an option is another argument for writing your own harness. Yes, you should do this. (Or at least customize the heck out of an existing one)

Share this:

It’s been about 5 weeks since the release of beta 2, so we’re very pleased to announce that Selenium 2.0b3 has just been released simultaneously for Java, .Net, Ruby and Python. You can download it from Selenium HQ or from the Google Code site. This release focused on providing excellent support for the next generation of browsers, particularly IE 9 and Firefox 4, and we think you’ll like what you’ll find.

• Restructured documentation at Selenium HQ
• An improved user interaction API
  • Including experimental IME support on Windows.
• Alerts and prompts handling for IE.
• Marked the following APIs as obsolete in .Net:
  • IRenderedWebElement.Hover()
  • IOptions.Speed
• Even more improvements to the Java webdriver-backed selenium
  • We’ll document the migration path before 2.0b4 is out!
• A significantly faster Android Driver

As well as these changes, there’s also the regular clutch of bug fixes and tweaks. For the number crunchers, there were a total of 331 changes that landed in the 5 weeks since the last release, with the 5 most active contributors working on each of the different languages supported by Selenium.

In addition to the enormous thanks that go to the developers, I’d like to add a big thank you to the Mozilla engineers who chipped in on the IRC channel at the last minute to help us work through some issues with Core. We’d not have been able to get this release out when we did without their help. Thank you Mozilla!

The next release will be focused on stabilization work, reducing our bug count and adding support for Grid 2.0.

Share this: