Skip to main content

The Software Artists: Explanation

I wrote a paper some time ago to submit to the Conference of the Association for Software Testing, but the paper was not accepted for the program. I'm on the waiting list if another presenter drops out, which seems unlikely at this point.

I think it is likely that my paper was not accepted at CAST was because it is somewhat similar to a presentation from Jonathan Kohl and Michael Bolton, two of the best testers in the universe. I intend to publish my paper here on my blog in the hopes that Jonathan and Michael and other Software Artists will have access to as much relevant information as possible to support their position.

I think that one enormous reason that few people take software-as-artistic-practice seriously is because of a perceived lack of practical application: manufacturing and engineering provide venerable examples of measurement tools, education curricula, and market strategy-- assuming that you believe that software is an engineered and manufactured product. Those of us who believe that software is an artistic process have failed to provide compelling alternatives to the tools provided by engineering and manufacturing.

I set out to start to remedy that situation with this paper.

It is a long piece, so I'll publish it in several sections in the coming days, as I have time to get it right and looking good. I have extensive references also. My plan is to publish references as separate blog posts after each section, so that people who don't care can skip them and people who do care can relate them to recent posts.

Comments

Scott Barber said…
Chris,

You could publish the paper in print form via the AST Newsletter if you'd like. Let me know and I'll get you the details.

Scott

--

Scott Barber
President & CTO, PerfTestPlus, Inc.
Executive Director, AST
Co-Author, Performance Testing Guidance for Web Applications

www.perftestplus.com
www.associationforsoftwaretesting.org
sbarber@perftestplus.com

"If you can see it in your mind...
you will find it in your life."
JonathanKohl said…
I don't know about CAST procedures, but I'm glad you are pursuing the paper. Michael and I are expanding on the ideas I expressed here: Exploratory Testing: Finding the Music of Software Investigation
Michael and I are drawing lessons from music and applying them to testing. I know you are looking at creating a school of thought around software artistry, so while the topics are similar, and compatible they are different.

Yours is a bigger picture view, and a systematic one, while Michael and I are learning more about testing by applying what we've learned from music. Our presentation ideas would probably fit within your system view.

If you're coming to CAST, we could sure use the help of a tester musician of your caliber. :)

-Jonathan
Shrini Kulkarni said…
Hi Chris ...

I have circulated these posts of yours to many of colleagues... I work for a IT services company in india as a Test consultant ...

In IT - software people (especially testers) are treated like low skilled labour ... they are ill treated even compared to thoese manufacturing industry ...

Your paper and blog posts need to reverberate and should get printed and heard in all communication channels in India. This would spread awareness in india about state of Software people ...

Shrini
http://shrinik.blogspot.com

This blog site is pretty good ! how was it made . I view something genuinely interesting about your site so I saved to my bookmarks . you can visit my site .
coworking space mountain view

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.