I've been nominated as a director candidate for the CMG. My candidate statement is posted below because my views related to CMG mirror my views for application performance in organizations and the industry as a whole and I believe that is (or, at least, I hope it is) interesting to anyone involved or concerned with challenges related to application performance now and in the future.

If you are a CMG member, I encourage you to review all of the candidate statements and to vote your conscience here.

This past weekend, I finally made time to start reading Agile Testing: A Practical Guide For Testers And Agile Teams, Lisa Crispin & Janet Gregory, Addison-Wesley (2009).  I made it through the first two chapters before life called me away.  After I put the book down and starting going about accomplishing a mundane series of errands, I realized that I was feeling disappointed and that the disappointment had started growing just a few pages into the book.  Not because of what the book had to say, what it said was pretty good – not exactly how I would have expressed a few things, but thus is the plight of a writer reading what someone else has written on a topic they also care and write about.  What was disappointing me was the fact that the stuff in those chapters needed to be said at all.

Last week, I hosted STP's Online Performance Summit, a 3 half-day, 9 session, live, interactive webinar. As far as I know, this was the first multi-presenter, multi-day, live webinar by testers for testers. The feedback from attendees and presenters that I have seen has all been very positive, and personally, I think it went very well. On top of that, I had a whole lot of fun playing "radio talk show host".

The event sold out early at 100 attendees with more folks wanting to attend, but were unable. Since this was an experiment of sorts in terms of format and delivery, we made a commitment to the smallest and least expensive level of service from the webinar technology provider, and by the time we realized we had more interest than "seats", it was simply too late to make the necessary service changes to accommodate more folks. We won't be making that mistake again for our next online summit to be held October 11-13 on the topic of "Achieving Business Value with Test Automation". Keep your eyes on the STP website for more information about that and other future summits.

With all of that context, now to the point of this post.

Yesterday, SOASTA announced their new product, CloudTest Lite (Press Release). It's not common that I get excited about a tool product release, but this is different. This product has the potential to change the market for the better.

Scratch that. I'll be shocked if it doesn't change the market for the better.

Why is that, you ask? Consider the following attributes of CloutTest Lite:

• It's a fully featured, easy to learn and use, enterprise class, modern, performance testing tool for web & mobile applications
• All you need to use it is a reasonably modern machine connected to the internet and a web browser.
  • You don't need to buy, install, configure or maintain load generation machines.
  • The "license" is tied to your personal credentials, so you can design, create, execute, and analyze your tests from any machine you want without needing to figure out how to point to the license server, or how to get onto the corporate network from your favorite internet cafe.
  • You can even do much of the design, test enhancement, and analysis entirely off-line.
• You can simulate up to 100 virtual users any time you want. No more scheduling time on the controller days or weeks in advance guessing the app will be ready for your test. No more having to wait until your next scheduled time to re-run your test when you see something 'wonky' in your data.
• It's free.
  • Yes, I said free.
  • As in, you never need to pay a dime. Not today, not when the trial expires, not a year from now to continue your maintenance contract.
  • That's right, it is free from now until the sun explodes (or at least until well beyond when anything we're building or planning to build today is long gone and forgotten)

Imagine the implications:

I guess it’s that time again.  What time is that, you ask?  It’s the time when discussion/debate flares up over Context-Driven. I’m not going to weigh in on the whole discussion of pros/cons, value/distraction, etc.  I am a consultant.  I am Context-Driven (and not just as a tester, it's simply the way I have operated since long before I was a tester and long before I became aware someone had coined a term and composed a set of principles around how I already operated).  The license plate on my car says “CONTEXT”. It works for me.  But my point isn’t to convince you that it’s right for you.  My point is to address a comment that I frequently hear that *feels* very sad to me.

“Where I work, I don’t have the freedom or authority to implement all this Context-Driven stuff, so I guess I don’t get to be part of the club.”

I find this sad, because I don’t agree.  It is my opinion that “Where I work, I don’t have the freedom or authority…” *is* a "driving context", making smart decisions about what you are empowered to choose, and appropriately trying to inform/educate those who are "driving your context" that there are other options qualifies as being Context-Driven... at least to me.

uTest is doing a series of interviews with interesting/well-known testers. I was flattered to be asked to be interviewed recently and found that I enjoyed answering the questions... and didn't hate my answers when I read them as posted (any of you who have ever done that sort of thing know that is a fairly significant statement!)

My interview is "Testing the Limits with Scott Barber": Part I, Part II, Part III

I was pleased to see Michael Bolton's series on Testing vs. Checking. If you haven't been following, what I consider to be the central thread of the topic (and the unfortunately inevitable fallout that seems to happen in "testerland" almost any time someone says something that makes sense).

From Michael:

• http://www.developsense.com/2009/08/testing-vs-checking.html
• http://www.developsense.com/2009/09/transpection-and-three-elements-of.html
• http://www.developsense.com/2009/09/pass-vs-fail-vs-is-there-problem-here.html
• http://www.developsense.com/2009/09/elements-of-testing-and-checking.html

From James Bach:

• http://www.satisfice.com/blog/archives/358

From Scott Barber:

• http://www.perftestplus.com/resources/014PeakPerf.pdf Original, ST&P Magazine, 2005
• http://www.logigear.com/newsletter/investigation_vs_validation.asp Reprinted by Logigear, 2007