Selenium Blog

Aside from one of the dog’s tummy making noises that imply a big mess to clean up later, this scheduling thing seems to be working out.

• Heard someone talk about doing bitmap comparisons last week somewhere. Adaptive Images tricks I suspect are going to become more commonplace. Good luck with that. Se is best at interaction, structure and content checks; not does-it-look-the-way-some-human-intended. Robots where robots should be used. Humans where humans should be used.
• Interacting with a Javascript confirmation from Selenium in Cucumber
• Converting Selenium waitForCondition to WebDriverWait sends you along the path to understanding Waits in WebDriver
• Splinter seems like a wrapper about the Python WebDriver bindings
• Making a Mockery of TDD starts with To be a successful mockist, you must dislike mocks. which I think is just as important when doing Se. The res of the article is good too.
• Integration Testing with RSpec, Capybara, and Selenium includes this gem

  Integration tests can be brittle if they know too much about how those components work. Proper integration tests use your application as a black box. They should know as little as possible about what happens under the hood, they’re just there to observe and interact with the interface.

• I seem to think I already posted this, but the search isn’t finding anything. Here is a visualization of the commits to Se.
  
• The GoogleWebmasterHelp channel on YouTube is full of ideas that you could include in your scripts. At least from an SEO perspective. And Google SEO at that.
• The theme this week seems to be GIL. So here is About concurrency and the GIL which for once is about Ruby.
• The whole ‘Facebook switching from Watir’ thing produced at least one good rebuttal; Facebook, Watir And Testing

Share this:

Trying something new; queuing up the catch-up post while I have time to catch-up.

• I’ve been lead to believe that Functional Testing with Arquillian is a Big Deal&tm;. Of course, I just see a lot of Java…
• If one thread raises an exception, why aren’t other threads’ finally blocks called? is an interesting question with a nice answer. If you start running scripts in parallel, this, and the GIL is something to keep in mind.
• My favourite part of posts like Using Test Oracles to Ensure Your Tests’ True Validity is they always have a ‘this is how I learned this the hard way’ story in them.
• I’m getting more and more convinced that the route to WebDriver powah! is through the JavascriptExecutor. As illustrated in setContext(..) is back for Selenium2 😛
• One important trick to maven is knowing how / where to bind server control to. Testing webapp startup on Jenkins using Maven, Tomcat and Web Driver might be a bit grand a title, and is using HTMLUnit (why?! do your customers use that browser? really?) but illustrates the maven part well.
• Since we’re in the HTML (findin yur bugz) whilst automating anyways, You’re Doing it Wrong: Common HTML Tag Misuses is something to keep at the back of your mind.
• And since we’re critiquing the HTML, why not how the database schema is designed and its impacts on API design. Identifiers are not numbers
• Patchwork is a library that lets you monkey patch in PHP. Haven’t found a need for it yet, but I keep thinking I will.
• Making Facebook Self-Healing is just darn cool. And unfortunately most things in the Immunization/Healing space are highly customized and not really candidates for open sourcing.
• Taking screenshots with Selenium WebDriver in C#

Share this:

How did I fall behind again already?!?!

• This is a pretty good deck. Automation Isn’t All Shiny Toys
• If your work is divided in time-based goals then providing videos of the end result is a fantastic idea. See Dave’s Q3/2011 in review. The last two screencasts directly relate to Se
• The training wheels came off is outstanding! I’ve been saying this around Se-IDE for years.
• If you have tried automation-in-anger with Python, then you have likely spent some time swearing at the GIL. Thankfully David Beazley finds the GIL ‘fun’ and has posted some slides about it. here and here. Such geeky fun.
• Feature Switching is an important concept to get your development team wrapped around if doing automation; Feature switching: a better way to collaborate even has a common project feature-switch-inated linked to at the end.
• Another important thing is hosting your own respository of build artifacts. Repository? That’s not a repository
• Logging Selenium 2 Events in Twist is a product centric spike report — but is a good read if you want to extend WebDriver
• This ‘Learn your tools’ reminder is brought to you by diving down the stack
• Automated configuration management with Puppet? Geppetto seems to be an important addition to that toolset.
• The 5 steps to the parallel web testing epiphany

Share this: