Skip to main content

CFP: Peer conference "Writing About Testing" May 21/22 Durango CO

CFP: Peer conference "Writing About Testing" May 21/22 Durango CO

I am organizing a a peer conference for people working in software testing and software development who write about their work in public. The conference will be organized LAWST-style, much like the recurring Austin Workshop on Test Automation or the Tester-Developer/Developer-Tester conference I helped organize in 2007.

The original proposal is on my blog here:

There is significant demand for public information about software testing and software development and software process. This conference is for people who want to influence the public discourse on these subjects through public writing.

If you are interested in the subject, but not necessarily interested in the peer conference, there is a private mail list for writing about testing whose members include both writers and publishers. I (or any other member of the list) will add you to the mail list if you send us your email address. I am at christopher.mcmahon on gmail. Your email will be used for no other purpose than to join the list.

New voices are particularly encouraged to apply for the conference and to join the mail list. If we don't know you or your writing, please point out links to some public examples like blog posts, public documentation, conference papers, or similar work when you do so.

A number of prominent writers and also new voices in the software testing community have have expressed interest in attending the conference. In an effort to break down some of the wall between writers and publishers, at least two publishers of software testing material also have expressed interest in attending. The conference will have a definite agile slant, but I don't want to exclude great writers working in other situations.

This peer conference is run like many others: send a position statement saying why you want to attend, and what relevant material you would be prepared to contribute to the conference. Examples of relevant material might be a presentation, interesting experience, or even a really good set of questions. People will be invited based on those position statements. As of now, I will be the one evaluating these, but I will be sharing them freely with others on the mail list whose judgment I trust. Even better, join the mail list and publish your position statement there.

I may or may not cap attendance at 15. If we get a significant amount of great position statements, I might increase that number.

There will be no fee to attend, but you will be responsible for your own transportation and lodging. A discounted rate at a convenient bed and breakfast hotel within walking distance of the conference will be available for a limited number of rooms.

Here are the relevant dates:

Dec 1 2009
Deadline for position statements to be emailed to me or to be posted on the writing-about-testing mail list.

Feb 1 2010
Invitations to the conference sent. Waiting list established if necessary.

May 21 and 22 2010

Durango has a lot to offer visitors. Attendees may want to arrive early and stay late. The Taste of Durango street festival is Sunday May 23, and we also plan to have an outdoor excursion that day. There will likely be a number of attendees driving from the Denver area Thursday May 20, so carpooling from Denver or Colorado Springs could be possible for the 6-8 hour drive. Direct flights to Durango are available from Denver, Phoenix, and Salt Lake City, or the Albuquerque airport is a 4 hour drive in a rental car. Let me know if you need more detailed information about getting to Durango or about the conference itself.

UPDATE: I have just been informed that there is no longer a direct flight to Durango from Salt Lake City. United, Frontier, and USAirways fly to Durango from Denver and Phoenix.


TestWithUs 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.