A Smattering of Selenium #30
I’ve missed a couple weeks due to travel and a complete system lock which meant I lost all the links I had open but not saved.
Categories:
I’ve missed a couple weeks due to travel and a complete system lock which meant I lost all the links I had open but not saved. So these are the ones I have recovered.
- I have written a series of posts on how to do parallel execution of tests in JUnit 4 up on the Sauce Labs blog. Part One, Part 2 and Part Three
- Quick start with FitNesse and Selenium is a beginners guide to wiring Selenium and FitNesse together. Though it might have been easier to just use Selenesse
- Meetup: Test Automation Tips, Techniques and Best Practice – Ruby and Java night in NYC, November 8
- Commit 10000 for the Se project. That’s a non-small number
- If you are using Maven 3, you can now use the Selenium Plugin with it now.
- Do Testers Have to Write Code? applies to Se as well.
- Multiple Sessions in Cucumber & Selenium got a fair bit of twitter love and is something I’m seeing clients want/need more and more
- A Set of Principles for Automated Testing is not a bad list. I completely disagree with the second one, and the last one is blatant employer promotion (but is contextually correct).
- RSpec best practices is a similar list which I have less complaint about. The third point is likely the most important one.
- Multiple Sessions in Cucumber & Selenium is a solution for when you are testing something with WebSockets with Cucumber.
- NUnit 2.5.8 is out.
- Dale Emery has released Runtime Suite which is super handy for creating test suites at runtime with JUnit 4. It doesn’t (yet) work with parameterized classes, but is still pretty cool
- Feed4JUnit seems to have don’t some of the legwork for people to do parameterized JUnit scripts. (Yes, I’ve been stuck in Java-land for the last while; why do you ask?)
- As Flex Pilot gets more usage, things are starting to trickle out into the blogs. Automating MyAppInFlex.swf – Useful FlexPilot commands is one of those posts.
Oh, and both 2.0a6 and 2.0a7 have been released. We’re getting closer to the ‘API freeze’ which will mark the end of ‘alpha’ and the start of bug fixing (beta) for the final release.
