A Smattering of Selenium #128

…as I avoid writing code that deals with dynamically constructed tables. Without any sort of unique locator. Of course.

• I would contend that the ‘right’ solution to this problem is to use a CI container and have it email you, but if you are using Java and not using CI, then Automatically Email the Reports After Selenium Test Execution could be valuable.
• I feel like I have already linked to Webdriver StaleElementReferenceException but the archive search is, erm, not great, so here it is again. Notice the solutions to what are all synchronization problem is not to turn on implicit waits.
• A lot of the reason for lighting up a browser is to be able to do input with the app; The CHECKS Pattern Language of Information Integrity is useful reading in this regard
• While I wait for MS to send me a free Surface to play with (*hint*), Testing Applications by Using the Surface Simulator Automation API seems like they have at least given the problem some thought. Of course, it starts with a hand-holding of how to use an IDE. How very Android of them.
• Inspect the State of Your Running iOS App’s UI With Symbiote — Essentially Symbiote is Firebug for your native iOS app.; you gotta love a good elevator pitch
• I don’t the Opera kids get enough credit for what they’re doing (and did first iirc) – Introducing mobile browser automation
• If you brain didn’t hurt yet, it will now. What’s the difference if “" exists or not?
• OAuth2 seems to have died a public flaming death, so some smart folks created oz. There is some snark I can’t find about not liking a fork so creating a new one and now you have n+1 problems or something… All auth system suck BTW.
• Ivoire has some RSpec goodies — but in Python
• What? You’re not using data-* attributes yet? Shame on you…

• Previous
• Next