Monday, December 06, 2010

Bug Tracking System for Busy Testers

WARNING: This one-idea-a-day series are typically 10-minute writeouts of my 40-min whim while I'm running on treadmill. They serve the purpose of givign me the joy of day dreaming and writing something every day. The ideas here will have very high probability of being total crap. Read at your own peril.

I've been discussing with a friend about a team collaboration tool idea based on Google Wave a while ago. Today I'd like to reduce the scope much and focus on an area that I'm familiar with: bug tracking system for software projects.

Why?
We don't have dedicated testers, so everyone is a tester whenever he's got some free time. Sometimes we are lazy (aka too busy), and don't want to go through the full-blown bug reporting UI to enter bugs one by one. So the typical bug reports would become a single email or wave:

Hey guys, I've found the following issues:
1) The app crashes when XXX
2) The phone ate my cat when XXX
3) The app not working, and knocking the phone on the wall didn't help.

Obviously, this type of bug reports are hard to track. And even if someone who's dilligent enough to create separated tickets for each report, it's quite possible that we are gonna loose the context -- the whole email itself.

Features:
- Allow filing bug reports in a big ticket. Developers (or not that busy testers) can select some text and click a button to turn the selection into a new "subticket", in case there is need to track each individual "subticket".
- In the original ticket, each selected part would have a hyperlink to its "subticket", and the status of each subticket is displayed inline with the text.
- Send an email to the bug system, the system creates a ticket automatically.
- auto-detect and format special elements in reports such as stack trace.
- Each ticket is a wave.
- The same cool text editor from Google wave: intuitive text entry, easy to attach images, etc
- The same real time communication goodness coming from Google Wave.


No comments: