DAMMIT!!! Five for Friday – July 1, 2022

A twitter follower just told me that my five for friday didn’t show up. Yes, I’ve been busy, but mostly just dumb, as I somehow managed to write this, and not post it.

Better late than never.

This week has …not really been any better than last week. Lots of things happening, and only some of them are good. I still found a few bits of information worth sharing.

I hope something here is interesting for you. See you next week!

Similar Posts

  • Don’t like something – fix it

    Perhaps it’s just the nature of the tester, but I’ve seen a lot of complaints from testers recently. “Managers do the wrong thing”, “Testers need to do more ‘x’”, “Testing isn’t taken seriously”, “These people don’t understand what I do”, gripe, mumble, etc. Of course, it’s easy for me to tell you to quit your…

  • Conferences – again!

    I took some time off from speaking (too much) at conferences over the past few years. I spoke at TestBash Philadelphia a year ago (and also spoke at the Online Test Conference last summer), but 2017 (and, IIRC, 2016) have been light on me in terms of external speaking. But I’m going to kick off…

  • Conflicting Results

    I’m a huge soccer fan, and I’m happily following the MLS Cup even though the local team was eliminated last week. Last night’s match between Real Salt Lake (RSL) and the Chicago Fire went to penalty kicks before one team finally prevailed. After the game ended, I went to mlsnet.com to watch the highlights and…

  • Design for *GUI* Automation

    I’ve stated my distaste for GUI automation before, but after my last post, I feel the need to share some clarification. I’ve been meaning to write this post ever since I wrote GUI Shmooey, so here goes. First off, let me state my main points for disliking GUI automation: It’s (typically) fragile – tests tend…

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.