Technical Testing at the Online Testing Conference

It’s Friday, and it’s time to share five things I thought were interesting this week. That’s all for this week – I’ll try again in seven days or so.

Status meetings are boring. More importantly, status meetings are unneeded. Meetings are for discussion, and updates on status rarely require that (until, of course, they do). Nothing – nothing is more painful than sitting through a meeting where people go around the table and say, “Today, I’m doing X”.  Hopefully nothing alarming so far. A lot of teams…

Back again and sharing a few cool things I found this week. I wrote another article for TestProject – this one on why developers should write all (or at least most) of your automated tests. While I’m self-promoting, I’m giving a webinar next Wednesday on developer vs. tester mindsets. Former guest on the ABT 343…

A lot of people, both co-workers and not, have asked me why I “chose” Unity for my post-Microsoft career. Although I documented (sort of) why I broke up with Microsoft, and talked in a few other places about my role, I guess I haven’t publicly shared why I’m at Unity (vs any other tech company)….

People talk a lot about how they got into testing (I was told I was a tester on my first day at a tech support job), but for those of us who have been in testing roles for a substantial amount of time, I think it’s equally important to think about why we have stayed in…

The background: I posted some thoughts on how I approach test strategy and what the term means to me a week or so ago. The Rat Pack had some questions on the post and I answered them. But the conversation made me realize that it may be beneficial if I take some time to talk…