Tejas Software Consulting Newsletter

August/September 2004, vol. 4, #4

Can you Q&A this over the weekend, so we can launch on Monday? -malapropism submitted by Mark McWhinney
If you can't figure out why that's funny, see the Feedback section for the background. Welcome back to my newsletter. I'm a consultant and writer focusing on helping software development organizations manage the quality of their products by doing testing.

If this has landed in your email inbox, thank you for signing up as a subscriber. If you know someone else who might enjoy what you see here, feel free to forward this issue as long as you keep it all intact. And if you aren't yet a subscriber, please consider visiting http://tejasconsulting.com/newsletter/ to see how to sign up.

In this month's feature, I tease you with a mention of a few different tools while discussing the underlying infrastructure that makes them interesting, and I invite you to a discussion about more of the details.

-Danny R. Faught, Software Alchemist
faught@tejasconsulting.com -- http://tejasconsulting.com/ -- +1-817-294-3998

Contents

Tejas Newswire

The "Stress Test Tools Survey" is the latest feature available on Open Testware Reviews. Also, these features are now publicly available: QMTest review, Data Comparator Survey, Technology Bulletin: System Call Hijacking Tools, and  Screen Capture Tools Survey.

My StickyMinds column "Meaningful Connections" was posted July 26, 2004. In the article I continue to explore the topic of social networking.

As a reminder, I'm speaking at these conferences soon. Let me know if you're also planning to go.
I've recently had the opportunity to speak about open source tools at the Dallas/Forth Worth Unix Users Group and the Fort Worth Java Users Group. I'm lining up some other local speaking engagements - sign up for the metro-sqa mailing list if you're in the area and want to get the details when they're finalized.

Feature Article
Software I Don't Install

I have become a fan of software that I don't have to install. Maybe you've heard of "Application Service Providers" (ASP's) that make this possible. But this term doesn't appear anywhere on the web sites of the ASP's I've started using. More on that in a minute.

Here's what led me down this path. I'm working as a Software Project Manager for a small project. The client asked me to pitch in to help the overloaded IT person in my spare time. But it quickly became clear that there would be no spare time, and in fact I needed to hire extra people to help with software development on what was actually a not-so-small project.

Still, I wanted to help the IT guy if I could, and the opportunity arose when I started evaluating tools to handle bug tracking and change requests. I knew that there were several bug tracking tools that were hosted on the vendors' web sites. No installation required, no server to maintain. Just log in using a web browser. Also, with a web site outside the company's firewall, the customer, contractors, and remote employees wouldn't need to go through the company's firewall to get to the server. If I could find one of these hosted tools that worked, then I wouldn't have to add another task to the IT guy's workload. So that's what I did.

After reviewing a dozen or so tools listed on testingfaqs.org that are available as an ASP, I chose a tool called Squish. (Not to be confused with Squish, the GUI test tool, which I coincidentally recommended to another recent client). And Squish accomplished something that no other bug tracking tool has done for me before - I liked it right off the bat. I liked the way I could easily reorder the fields and add new ones. I liked that it worked as well with Mozilla as as it did with Internet Explorer. I liked the fact that I could download a complete copy of our data in XML format. And I really liked the 120-day free trial period with an unlimited number of users. After the trial, the pricing is very reasonable compared to similar tools. My second choice was Elementool.

Limits

After having used Squish for about a month, I'm more aware of the limitations. The search feature is too simplistic, not letting me choose more than one thing to search for in a field. It's too hard to filter out resolved bugs. The vendor doesn't back up the data, and I'm not sure if they can restore a backup from the XML export. Some of the formatting in the description field is not maintained in the exported XML data, which means we can't easily restore the database exactly to its original state from the XML export. But like all the other bug tracking tools, I learn to work around the limitations, and for everything else, I export data to a different tool to do further processing (Squish can also export some of the fields to a spreadsheet, and the "print" button produces a nice HTML rendering if you ignore the print dialog that pops up).

One thing I looked for in a hosted tool is an option to buy a locally installed version the software. A handful of the hosted tools offer this, giving the option to buy a license and stop paying subscription fees, but Squish isn't one of them. Also, a factor to consider for any hosted tool is security. While the data is transmitted over an encrypted connection, we're still trusting the vendor with our data. This would be a problem for companies that are very sensitive to any potential leaks of proprietary information.

I considered open source options for bug tracking tools. Of course, maintaining the software on a server and providing network bandwidth for it goes beyond having free software. I tried to set up an open source bug tracking tool myself on a server that I have in my home office. I already had the CVS version control software running there for the client over a secure shell (SSH) link. I tried to run the bug tracking tool, Mantis, on the same server, but I found that it won't work over a forwarded SSH port. Later I heard that there are commercial providers who use Bugzilla, a popular open source bug tracking tool, including bugTracker, Bugopolis, and hipergate.

More software I didn't have to install

Here's another recent example of the benefits of hosted software. A new manager on the project was asking if we had any project tracking software in-house. The answer was no, and while we could buy what we needed, the one IT guy was in Europe for three weeks, and only he had administrative access to the company PCs. I did a quick search for hosted project tracking tools, and recognized AceProject as one of the tools I had looked at when I was evaluating bug tracking tools. I had felt it was too focused on project management to be a good bug tracking tool, but I recommended that the manager evaluate its project tracking features. Within minutes, she had established a project in the software and was entering data. No administrator required.

Yet another application that we probably don't think of as ASP software is our email client. I bet most of us have found ourselves using someone else's computer or someone else's network where we can't get our email the way we normally do. But all it takes is a web-based email interface to save the day. No need to configure someone else's computer or tunnel a forbidden protocol through a firewall - just log in with a web browser, and when you're done, it all goes away when you log out. Granted, for corporate email systems, it's not technically an ASP if the company maintains the server, but the important fact is that it's a hosted service that's easy to reach anywhere on the Internet.

Whose server is it on, anyway?

So what do we call this type of tool, if "ASP" is no longer in vogue? The terminology seems to be splintering more as time goes on. I saw bug tracking tools that variously claimed to be "ASP-based," "hosted," and "subscription-based." I was confused when they used the term "web-based." All that tells me is that the tool has a web interface. For many such tools we have to set up our own web server to run it, but some vendors use "web-based" to indicate that the tool is hosted on their server.

Once I figure out that a tool can be run as an ASP, or hosted, or whatever, I now know that it might be just the ticket to get my project off and running with a minimum of hassle. Thanks to Alan Richardson for reviewing a draft of this article. If you'd like to discuss bug tracking further, I invite you to join the swtest-discuss mailing list.

P.S. Matthew Heusser pointed me to an interesting essay by Joel Spolsky. In the essay, Spolsky takes the position that the bug tracking tool his company sells should not allow the customer to add custom fields. This is heresy to most software testers, whose first requirement when shopping for a bug tracking tool is support for custom fields. But after reading and discussing the essay, I realized that I don't really need some of the custom fields I added to my Squish project. I've deleted some of them now. There are still a few tweaks that I've made that I really wouldn't want taken away, but I like the more simplified bug database I have now.

Feedback on the June/July issue and beyond

Here's the full context of Mark McWhinney's response to my comment about the rampant misuse of the term "SQA" (Software Quality Assurance):

My favorite has always been the use of "QA" as a verb.  Example: Can you QA this over the weekend, so we can launch on Monday?  For bonus points there is -- can you Q&A this over the weekend, so we can launch on Monday?

That just makes it even more ridiculous, doesn't it. Thanks for a good laugh. For those who aren't familiar with the terms - Q&A is an abbreviation for "question and answer," which you can guess is not at all the same thing as "quality assurance."

Michael Bolton made me aware of a fascinating five-year-old article on networking called "Six Degrees of Lois Weisberg" by Malcolm Gladwell. It gives an interesting counterpoint to my "Meaningful Connections" column. Here's one quote that touches on the need for diversity in your network -  "I hadn't seen him since I was seven. We had zero in common. It was wonderful."

Robert Pearson pointed out a recent article by David Strom, "Social networking may be the next social disease," which casts a critical eye on social networking services like LinkedIn. Strom says: "I think the whole concept is the next Internet sock puppet: something that is mildly cute and annoying."

Anne Wiser had this to say about my article "Homeschool Lessons for Everyone" -

It was a neat little article. I like the fact that it was written for a large audience, there's definitely some good advice in it like keeping kids intellectually engaged in learning during summer break. When I was a kid I always asked my mom to buy me homework books for the summer and when it was getting close to going back to school I couldn't wait to go back. I also like the idea of finding group learning opportunities for home-schoolers like museums and such because I bet they do need the social interaction with other kids (strangers - not just siblings or cousins) as well.

Thanks for sharing your experience. I've just read your "A Testing Career in 3-D" article and enjoyed it as well.

I appreciate the feedback. Socialization is a touchy subject for many homeschool parents, since the question comes up so often. In fact, the highly structured format of most public schools allows very little time for socialization over the course of a day. There are numerous opportunities for homeschool kids to build social skills, though homeschool parents have to take the initiative to take advantage of them.

I didn't get around to putting together an electronic copy of the article, but I do have a few more hard copies of the publication that I'd be glad to mail to anyone who'd like to see it.

After further discussion about homeschooling, Carl Nagle asked about two terms I used:

Perhaps you can elaborate on what you mean by "deschooling" and "unschooling"?

Deschooling is what we had to do during the year after my wife and I removed our oldest daughter from the public school system. She had to get over the trauma of not fitting into the mold they gave her, and she needed to open her mind to different ways of doing things. Many times she said, "But my teacher says we can't do it that way." Of course, some of this is natural any time a student changes teachers, but deschooling helped her to think more for herself. We don't have to worry about deschooling now, and in fact, it's easier for her to remember positive experiences in the public schools and to utilize some of what she learned there in her current studies.

Unschooling is a different concept. It's an unstructured approach to learning. The idea is to let the kids choose their own path and take advantage of their natural curiosity. Academic subjects aren't rigidly separated, and lessons often have a direct bearing on the things we need to do in our everyday lives. Many kids still need frequent guidance, because they don't naturally gravitate toward activities that parents would consider sufficiently educational. We are unschoolers to some extent, always watching for opportunities for learning and not planning a detailed syllabus more than a few days in advance. See The Unschooling Handbook by Mary Griffith for more information, and keep in mind that this is just one of a very wide variety of approaches that homeschool parents use.

Copyright 2004 by Tejas Software Consulting
#####

  Back to the newsletter index    Back to the home page