« February 2007 | Main | April 2007 »
March 2007
In development: Test case re-ordering
March 28, 2007
Last night I released Test Run 1.04, a version that contained a minor feature enhancement enabling greater interoperability with popular bug tracking systems. Tonight I started work on Test Run 1.05 which contains a single feature: the ability to re-order test cases within a test plan. This feature request comes after a number of customers expressed concern that their process required tests to be run in a specific sequence. However Test Run's default sort order (the created on date) was insufficient. They wanted more control then that.
So in the next version of Test Run, customers will be allowed to specify the order of their test cases within a test plan using a simple drag-and-drop interface. Stay tuned...
New feature: Non-numeric bug ids
March 28, 2007
A number of Test Run users, and wannabe users, use Jira, a bug tracking tool created by Atlassian. Jira is unique among other bug tracking systems in that the bug IDs it produces are not exclusively numeric. This made it difficult, if not impossible for those using Jira to integrate with Test Run's bug tracking capabilities.
So last night we released a few changes to enabled Test Run users to enter bugs into the system that can be any arbitrary string. So Jira users: rejoice. Test Run now works even better for you.
"The only viable on demand solution"
March 25, 2007
Tagged.com is one of Test Run's earliest adopters. Their team has been using the hosted version of Test Run for over a year now. They provide us with invaluable feedback to make the application better and we sincerely appreciate their business.
"Test Run was the only viable On Demand Test Case Management solution that provides a usable, flexible, comprehensive and reliable framework to manage tests. If you want everyone in your team to get up and running quickly, Test Run is the ideal solution."
A Better Way to QA
March 12, 2007
The past several years the Internet has been transformed by a slew of new web based tools and applications. A key success factor in all of these applications is adherence to a development methodology in which product teams release fewer features at a time, but release them at a greater frequency. Adherents to this methodology call this process “iteration.”
This methodology allows teams to:
- respond more quickly to customer feedback
- adapt the product based upon actual usage
- become more agile in the marketplace
However, this methodology requires a discipline that is difficult for many to obtain and maintain. That is because it is a radical departure for most software development companies who have deeply ingrained habits and cultures built up around more rigid and waterfall like approaches to software development.
For those that have made the transition to this Agile Development model, what is most intriguing is that while engineering teams and product management have undergone a tremendous process revolution the process of testing software has remained relatively unchanged. And for those companies, I ask you, how agile can your process be when chances are your QA engineers are still testing software the same way they did five years ago and ten years ago?
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.