Mike Kelly’s blog

We are starting planning for the September Indianapolis Workshop on Software Testing focused on the topic of testers who write code. Here are the details:

Date: Friday, September 26
Time: 8:00 AM to 5:00 PM
Location: Indianapolis, IN @ Mobius Labs

In this workshop we will focus on those aspects of testing where we write code. There will be a strong focus on performance, automation, and security testing. A lot of discussion around tools, languages, frameworks, and design patterns. We will be looking for experience reports from people willing to share project stories, examples, and we would be willing to entertain proposals for hands-on coding activities during the workshop.

If you’re interested in attending, please drop me a line. Preference will go to those who have experience reports to offer, but we always try to save space for people new to IWST and for people who are new to the topic.

The third and final article in my SearchSoftwareQuality.com Testing for Performance series posted. The complete series can be found here:

• Testing for performance, part 1: Assess the problem space
• Testing for performance, part 2: Build out the test assets
• Testing for performance, part 3: Provide information

David Christiansen and I did recently gave a webcast on SOA testing and some popular tools available. I really enjoyed giving the talk. It runs a little over one hour. You can find it here.

We also have an upcoming IWST on SOA Testing. If you have an experience you’d like to share, drop me a line. The workshop is free, the people are cool, and if I have my way we’ll have some sort of group exercise where we actually fire up some web services and test them. That reminds me, if you’re a company that has a web service that might be good for an exercise, you can also drop me a line. :)

Here is the 2008 lineup for IWST. This year, workshops are held on a Friday and run all day with regular breaks for networking and refreshments. There is no fee to attend any workshop. Email me at Mike@MichaelDKelly.com if you would like to attend.

SOA Testing
Date: Friday, April 25
Time: 8:00 AM to 5:00 PM
Description: In this workshop we will focus on testing in a Service Oriented Architecture. We will be looking for experience reports covering test planning and estimating; experience reports that talk about functional, performance, security, regression, and interoperability testing; and experience reports and demos that show off tools designed specifically for the SOA environment.

Testers who write code
Date: Friday, September 26
Time: 8:00 AM to 5:00 PM
Description: In this workshop we will focus on those aspects of testing where we write code. There will be a strong focus on performance, automation, and security testing. A lot of discussion around tools, languages, frameworks, and design patterns. We will be looking for experience reports from people willing to share project stories, examples, and we would be willing to entertain proposals for hands-on coding activities during the workshop.

About IWST:
The Indianapolis Workshops on Software Testing (IWST) are an ongoing series of no-cost workshops for experienced software testers and related professionals. IWST strives to build skills in software testing and allows people who are interested in topics in software testing to network with their peers. The emphasis is on mutual learning, sharing hands-on experiences and solving practical problems. In these meetings, experienced working practitioners discuss pertinent state-of-the-art topics. IWST has been organized by a small team of local practitioners in the field of software testing.

When testing web services it’s often nice to be able to process a set of XML files. In other automation it can be nice to process batches of files as well. For some reason I can never find the following code when I need it and I always have to re-code it from scratch. That’s always good practice, but it’s annoying when I need it quickly.

def getFiles(directory)
returnFiles = []
Dir.glob(directory + ‘/*’).each do | file |
if File.file?(file) then
returnFiles.push(file)
else
returnFiles.push(getFiles(file))
end
end
return returnFiles
end

So there it is. Google can now help me find my code whenever I need to build a list of all files in a directory structure.

Here is an example of how I might use that:

getFiles(”C:/Regression Files”).each do | testCaseFile |
resultsFile.puts(testCaseFile.to_s.split(’/')[-1].chomp +
‘, methodName, ‘ + object.methodName(testCaseFile))
end