Skip to main content

Testing Summit at Telerik

I attended the Test Summit peer conference this weekend at the invitation of Jim Holmes of Telerik.

It was outstanding, as such peer conferences tend to be, and I and others will be posting a lot of information as a result of what went on there. 

But I want to talk about the conference itself. 

Software testing has a long history of peer conferences, starting (to the best of my knowledge) with the Los Altos Workshop on Software Testing (LAWST).  Bret Pettichord borrowed the LAWST format for his Austin Workshop on Test Automation (AWTA) in the mid-2000s, and I borrowed from AWST for my Writing About Testing (WAT) conferences in 2010 and 2011.   I think other examples exist.  The format has gotten looser over the years.  LOTS looser, as we find that motivated participants are pretty good at self-organization.

As far as I am aware, the Telerik Test Summit (TTS?) is the first such software testing peer conference created and sponsored by a commercial company.   I think this is important, and I think TTS has important implications.

As a general rule, I will not endorse or support commercial companies, even the ones I work for.  I don't even link from blog posts to my own writing for articles that are behind a registration-wall or pay-wall.  Now that I work for the Wikimedia Foundation, I have even more motivation to be as impartial as I possibly can. 

And yet I accepted the invitation from Telerik and Jim easily.  I'd like to explain that. 

I knew everyone in the room at TTS, and many of the attendees are good friends.  I had never met Jim Holmes. 

But I knew his work.  Jim created the CodeMash conference, which is notable not only because of its radical growth in popularity over the last several years, but also because of its reputation for friendliness and hospitality.   I'm not involved in CodeMash and I've never attended it, but I know a lot of people who have, and Jim has a stellar reputation among my friends and acquaintances. 

I didn't go to TTS because Telerik invited me;  I went because Jim Holmes has an unimpeachable reputation for integrity and hospitality. 

We were not pitched. We were not marketed to. There were no Telerik tools being discussed in the room.  We were given a tour of the Telerik office in Austin;  some attendees chose to pair up with Telerik staff to see what they were working on, some did not.   I consider this just hospitality. 

TTS should be a lesson to other companies.  Many of the best people working in software will give away their best ideas and even their best work freely.   But the moment such people suspect they are being used or co-opted for some purpose other than trying to move the cause forward, we will turn on you with a vengeance you can not imagine. 

So my advice to any companies who might want to sponsor their own peer conferences in the future:  first, get yourself a Jim Holmes; second, listen to what he has to say; then, do what he tells you.  That's probably harder than you imagine.


Marlena Compton said…
Although I hadn't thought about it previously, it really is a big deal to have a company plan a conference this way. It goes back to the philosophy of one of my favorite bosses, "hire really smart people who can get along, trust them and things will work out." In this case it was to gather some really smart people who get along and trust them.

It was a privilege to work with Jim, you and the others at this conference.
Jim Holmes said…

Thanks for the kind words. I'm fortunate to have landed at Telerik where the culture and management is completely supportive of this approach. I really appreciate you calling this out, because it's a rare mindset.

It was an amazing weekend, and I count myself as incredibly lucky to have spent it with y'all!
Phil Sams said…
I did not previously know anyone attending the testing summit at Telerik, except for working with Jim. However, working with Jim, I have come to trust his judgment without question. I found the folks attending the summit to be open and honest, two traits I value highly, and incredibly smart/bright in their specific subject areas. I learned something from each of the attendees, and hoped I contributed just a little. I too feel fortunate to have landed with Telerik and with the super folks that work there.

I wanted to thank everyone at the summit for the opportunity to listen, learn, and participate.
Deitrich said…
This comment has been removed by a blog administrator.
Carl said…
Hi Chris, We met at in 2007 at AWTA. I would love the opportunity to listen to your presentation. What would I need to do to attend the Telerik Summit? If I am unable to attend the conference I would welcome the opportunity to buy you a beer while in Austin.
TestWithUs said…
This comment has been removed by a blog administrator.
smith rose said…
This comment has been removed by a blog administrator.

Popular posts from this blog

Reviewing "Context Driven Approach to Automation in Testing"

I recently had occasion to read the "Context Driven Approach to Automation in Testing". As a professional software tester with extensive experience in test automation at the user interface (both UI and API) for the last decade or more for organizations such as Thoughtworks, Wikipedia, Salesforce, and others, I found it a nostalgic mixture of FUD (Fear, Uncertainty, Doubt), propaganda, ignorance and obfuscation. 

It was weirdly nostalgic for me: take away the obfuscatory modern propaganda terminology and it could be an artifact directly out of the test automation landscape circa 1998 when vendors, in the absence of any competition, foisted broken tools like WinRunner and SilkTest on gullible customers, when Open Source was exotic, when the World Wide Web was novel. Times have changed since 1998, but the CDT approach to test automation has not changed with it. I'd like to point out the deficiencies in this document as a warning to people who might be tempted to take it se…

Watir is What You Use Instead When Local Conditions Make Automated Browser Testing Otherwise Difficult.

I spent last weekend in Toronto talking to Titus Fortner, Jeff "Cheezy" Morgan, Bret Pettichord, and a number of other experts involved with the Watir project. There are a few things you should know:

The primary audience and target user group for Watir is people who use programming languages other than Ruby, and also people who do little or no programming at all. Let's say that again:

The most important audience for Watir is not Ruby programmers 
Let's talk about "local conditions":

it may be that the language in which you work does not support Selenium
I have been involved with Watir since the very beginning, but I started using modern Watir with the Wikimedia Foundation to test Wikipedia software. The main language of Wikipedia is PHP, in which Selenium is not fully supported, and in which automated testing in general is difficult. Watir/Ruby was a great choice to do browser testing.  At the time we started the project, there were no selenium bindings for …

Open letter to the Association for Software Testing

To the Association for Software Testing:

Considering the discussion in the software testing community with regard to my blog post "Test is a Ghetto", I ask the Board of the AST  to release a statement regarding the relationship of the AST with Keith Klain and Per Scholas, particularly in regard to the lawsuit for fraud filed by Doran Jones (PDF download link) .

The AST has a Code of Ethics  and I also ask the AST Board to release a public statement on whether the AST would consider creating an Ethics Committee similar to, or as a part of the recently created Committee on Standards and Professional Practices.

The yearly election for the Board of the AST happens in just a few weeks, and I hope that the candidates for the Board and the voting members of the Association for Software Testing will consider these requests with the gravity they deserve.