A Smattering of Selenium #65
Trying something new; queuing up the catch-up post while I have time to catch-up.
Categories:
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#
