We have already begun working on thi

Hi guys,

We are working on a complete overhaul of the test plan management system and I could use your opinion on something.

The idea for the new system is that there would be only 1 test plan per project. While a test plan can have multiple "components" that you use to organize your test cases, the idea is that you wouldn't have to juggle many versions of a test plan, some outdated, some partially up-to-date, etc.

What are your thoughts about this? Would it work for your normal usage?

Thanks,

Simon

This is now live. Please give it a try and let us know if you find any bugs. Thanks!

Interesting idea. What kind of tags did you have in mind? Can you tell me why you have multiple test plans? That would be useful for us to understand.

We are actually re-building the test plan management aspect of Lean Testing entirely. Development is ongoing and expected to take 2 or 3 weeks (maybe 4 with testing.)

In this new version, we will only allow 1 test plan per project. While a test plan can have various "components", the idea is to not allow multiple versions of a test plan and instead to have only one always up-to-date version of a test plan.

What are your thoughts about this way of working?

There are two reasons why we didn't do this by default:

1) It's easy to get lost if there's too many different statuses. When a project manager wants to know the status of his project, it's better if he doesn't have 15 different statuses to look at.

2) Say we added another, specific field called "reason" if the status is "closed". You might say it takes 10 seconds to fill it in, but 10 seconds times 1000 bugs a year adds up quickly.

I personally don't feel the value added is significant enough to justify this time.

However, I know I'm not always right and this might be super important for some users. We'll get to it, I just don't know when.

Thanks,

Simon