Test Run

Test Run, in one form or another, has been a pet project of mine for several years. But it wasn't until the past six months that I really believed what I had prototyped previously may actually be worth something. I originally wrote Testitool because the company I worked for at the time desparately needed some way for managers to gain a higher degree of visibility into the QA process. I spun off Testitool as an open source project, but do a really poor job of maintaining it.

I always felt that there was a real need for the kind of software I had created, but I simply didn't have the motivation to do what I knew had to be done in order to make it successful, easier to use, and more scalable: completely rewrite it.

But then, history repeated itself. I found myself, a project manager once again in need of software that would give those in my organization more visibility into the daily progress our QA teams were making at executing test plans. They also wanted a way to participate in the test planning process with the team and be able to add test cases to our test suite for future plans on their own. And finally, they wanted a tool that would automate much of the minutia that pre-occupied QA managers much of day. They prefered QA managers to spend their time actually writing test plans, not sending out daily reports, and making sure everyone knew what tests they were responsible for executing.

And so, I resolved to do what I had been putting off: make Testitool into a product worth using. Of course, I also had to change it dreadful name. Test Run was born. And over the past 6 months I have been nurturing this little piece of software, until now, where it is weeks if not days ready for a public beta.

I am excited. I believe in this software. Now it is time to see if others will too.