Test Run 1.1 Development Begins
September 28, 2007
Summer is over, the traditional slow time of the year in the software industry, and I have been getting a lot of renewed interest in Test Run. Customers have been submitting bug reports and a lot of feature requests, and many of them have in all honesty gone relatively unanswered in the last several months.
Well, that is about to change. I feel there is a critical mass of feature requests to begin working on Test Run 1.1. So last night work officially began. I have started to assess a lot of different things about the product in an effort to improve customer support and the experience around finding help. I upgraded the Test Run Blog and Knowledge Base to use Movable Type 4.0, and I have migrated Test Run's forums off of my personal web server onto the production Test Run machines. This has the added benefit of dedicating Test Run's forums exclusively to Test Run. Users will no longer find content related to my other software projects. This is a good thing.
As for what features I am planning for this release:
* At the top of the list is the need to integrate with popular bug tracking systems. This feature will allow users to submit bug reports directly into Bugzilla and FogBugz from within Test Run.
* An import feature for Test Link which will allow people to easily migrate to Test Run from that case tracking tool.
* Test Plan printing - many users asked for the ability to print a test plan to make it easy to review plans offline.
* Rich Text Editing - several users have asked for me to integrate a WYSIWYG editor into Test Run, and I will see what I can do to accommodate.
* Naturally there will be lots of bug fixes as well.
I encourage users to submit feature requests to me (as a comment to this post if you wish) and let me know what you would like to see out of the next version of Test Run.
About Byrne Reese
Byrne Reese is a product manager by day and an engineer by night.
He conceived of Test Run to help project managers like him stay up to date and informed of what his team was working on.