By James A. Whittaker
I am happy to report that attendance is way up at STAR. My back of the envelope calculations put it at several hundred more than STAR East a mere five months ago. A sure sign of economic recovery; I am surprised the stat hasn't made it to Obama's resume yet.
The Expo was my main disappointment. The vendor exhibits are still in atrophy. I realize the days of Mercury and Rational are over and Empirix's $ix figure rotating-parts booth is packed away in someone's garage, but there were only two short rows of sedate booths. (The magician was a nice touch though ... wish I could remember what he was selling.) Where have all the big players gone?
I gave a tutorial with the arrogant title (Lee Copeland's idea, not mine) "James Whittaker: On Testing." It was listed as sold out (STAR capped the audience at 100) but a couple dozen truants clearly snuck in. Apparently there is a bug in their 'sold out' exception handler and I am a poor door warden. The tutorial is a discussion of problems and trends in testing. I gave it at STAR East and it was different again this time. It's half a discussion of what we do wrong in testing and half about how to correct those behaviors. As my understanding of these issues evolves, so does this tutorial. If you attended (only a small handful of the 100+ would admit to reading this blog), feel free to post a comment, I promise not to delete any negative ones.
I had an amicable hallway conversation with James Bach. His blogger angst at my use of the title 'Exploratory Testing' didn't spill over to a face-to-face discussion. Frankly, I am not surprised. I've never claimed the term as my own, I simply took it and made it work in the hands of real testers on real software under real ship pressure. Consultants can coin all the terms they want, but when us practitioners add meat to their pie, why cry foul? Is it not a better reaction to feel happy that there are people actually doing something with the idea?
Yet I still made some jabs at the broader consultant community in my keynote. STAR remains full of vendors and people trying to sell ideas instead of results and good engineering practice. I am committing Google and the projects that I lead here to an openness regarding how we do testing and hope to be joined by others. I'd like to see the real practitioners, those who work at financial companies, data centers, ISVs, online retailers, and so forth to come out in larger numbers ... not just as the learners and attendees but also as speakers, panelists and active participants. I'm not saying the consultant community has nothing to say, those guys simply need no encouragement to open their mouths. It's the practitioners who I want to encourage. It's one thing to think really hard about testing, it's another thing to actually put those thoughts into practice.
The jabs aside, my keynote was aimed at describing the practice of exploratory testing I helped create at Microsoft and am now employing at Google and which is embodied in my new book. But it was my Google cohort Rajat Dewan who stole the show. After I detailed the Landmark Tour and how we applied it to Chrome, I ran out of time to talk about the FedEx tour. The folks at STAR were kind enough to set up an impromptu breakfast presentation for Rajat and he delivered a 20 minute talk to a standing room only crowd (I stopped counting at 150) on how he applied the FedEx tour to Mobile Ads. He showed three bugs the tour helped find and described how he automated the tour itself. (Has anyone coined the term 'automated exploratory testing' yet?)
Perhaps he can steal the show again by blogging about his presentation. Rajat?
Other highlights: apparently the twitter-verse was alight over my comment about god-the-developer. I don't tweet and I avoid twits at all costs so I am not sure if people were offended or found it insightful. Comments from tweeters? Also, I've been invited back for the tutorial at STAR East and also plan on submitting a track talk on How we test Google Chrome. Let the detailed discussion about real testing, warts and all, begin!
Permalink
| Links to this post |
5 comments:
"I had an amicable hallway conversation with James Bach. His blogger angst at my use of the title 'Exploratory Testing' didn't spill over to a face-to-face discussion."
hmm...interesting...are you sure about this though ?
lets wait for his next blog post ! :)
"Consultants can coin all the terms they want, but when us practitioners add meat to their pie, why cry foul? "
brilliant point...
"I'm not saying the consultant community has nothing to say, those guys simply need no encouragement to open their mouths. It's the practitioners who I want to encourage. It's one thing to think really hard about testing, it's another thing to actually put those thoughts into practice. "
Again....can not agree with you more...
I think our industry needs to be driven, MORE by people who actually DO/have done stuff rather than people who suggest stuff and are heavily inclined in so called oppposition bashing...
And i feel that there are loads are brilliant ET practitioners out there with wonderful actual stories to tell , but i guess they are busy in actual DOING real stuff :)
thanks
Having attended StarWest09 and participating in both of James' and Rajat's talks, originally I was disappointed with the first half hour of James' talk (no offense, but I don't need to know about your college history, it set some perspective, but I almost left cause the talk seemed to be going in a direction I didn't want to sit though), but then he got into the meat of his talk, the Plagues (which I have read here before) and 'Why You Should be Cheating When You Test". All I can saw is that I couldn't stop talking about it. I would love for Rajat to blog some more (his talk was almost more informative then Wed and Thur combined, for me at least). I sorta disagree with your statements about consultants, I think alot of the people at Star were less then prepared for good examples of solid engineering practices being done, too many of them were high-level process oriented people (my opinion on talking with lots of attendants). Having said that I would have loved to see more practical tracks and sessions. The idea of openness with Google testing is awesome, I can't say that enough.
I think the volume of exhibitors in the expo is simply a result of tighter budgets. From an IBM Rational perspective, I know we scrutinize every dollar we spend on conference booths (they're not cheap!) and we select only those where we think we'll connect with the most of our current, and hopefully future, clients. (STARWest I'll note, has always made the cut)
I spent many hours in the IBM Rational booth at the conference this year. For what it's worth, it was an interesting year where the majority of our discussions focused on process, not tools. Typically we spend 80% of our time talking about automation - this year we probably spent 80% of our time talking about team dynamics and getting people working better together to delivery quality software. Also - heard lots of great feedback on your tutorial and keynote. Sadly, our booth space doesn't get us in to the conference presentations. Hope you publish more on it here on the blog.
I was one of attendees who attended both of your talks in addition to Rajat's presentation. I am very impressed by the concept of tours in exploratory testing, I am looking forward to practice it my team and promoting it in the group. I completely agree with you regarding the plagues.
I also attended one of the panel discussion called the 'The Reality of Testing', which spent the whole time talking about the difference between Checkers and Testers.
Your presentation was great. You are true amazing person.
The part which I think was missing is some test sharing from the big Cellular companies on their test methods.
It would be nice to learn a bit how NOKIA\MOTOROLA\SAMSUNG\APPL test their mobiles (Unit and System testing).
These companies which have a lot of issues to overcome: Minimal memory sizes, Battery usage, Multiple CPU's on a cell phone and tons of features which all is being used while connection is up.
Why they ignore such knowledge sharing? Does STAR represent old testing? No one came to present and I do think that STAR and us need to think why.
Anyway, it was amazing hearing you and I will defiantly buy your books since the tours are a refreshing direction to me.
Thanks!
Post a Comment