A Smattering of Selenium #46
Selenium IDE on Firefox 4 is Available for Testing!
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
- 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