updating test plan with new version of test cases

dealforme · Post by **dealforme** » Thu May 10, 2007 8:05 pm

Hi,

Firstly, a great job by the TL team.

My apologizes if this is a duplicate because I've search the entire forum and Mantis and wasn't able to find this.

I'm trying to update my current test plan with a newer version a test case. I didn't see a means of doing this so I had removed this test case and re-applied which worked fine. But doing so I've lost the historical execution of this test case (I know this has been discussed already in another thread).

Should I enter a Mantis item to have this feature included or is it in the plans?

L Wong

Post by **fman** » Fri May 11, 2007 7:10 am

This is standard behaivour.
You need to create a NEW TESPLAN to use a NEW test case VERSION, you can not have historical information of execution of DIFFERENT TEST CASE VERSIONS.

In the meantime (and may be never) we are not going to change this behaivour.

Regards

dealforme · Post by **dealforme** » Tue May 15, 2007 4:06 pm

fman wrote:This is standard behaivour.
You need to create a NEW TESPLAN to use a NEW test case VERSION, you can not have historical information of execution of DIFFERENT TEST CASE VERSIONS.

In the meantime (and may be never) we are not going to change this behaivour.

Regards

Thank you for your response and TL stance on this subject.

This is unfortunate from my perspective. Normally we consider test cases living document and constantly changing. This also make the build feature redundant now. The following is what I had hoped TL would behave.

Post by **fman** » Tue May 15, 2007 4:35 pm

Our point of view is this:

think in a build as a version of object undertest, i.e. Test Link 1.7.0 RC1

the set of test cases I want to run are the test plan.
When 1.7.0 RC2 is ready, I want to apply the same test cases I have applied to 1.7.0 RC1, nut what I want is having a different group of results, that why I create a new build.

IMHO having different version of Test Cases on the same test plan is confusing.

You have another possibility: allow editing of executed test cases.
In this way you loose info about version, but can run build 2 against the
updated test cases.

I would be interested to know how other test management tools manage
the situation you have despicted.

dealforme · Post by **dealforme** » Tue May 15, 2007 8:22 pm

fman wrote:Our point of view is this:

think in a build as a version of object undertest, i.e. Test Link 1.7.0 RC1

the set of test cases I want to run are the test plan.
When 1.7.0 RC2 is ready, I want to apply the same test cases I have applied to 1.7.0 RC1, nut what I want is having a different group of results, that why I create a new build.

What you have described makes perfectly sense.

fman wrote:IMHO having different version of Test Cases on the same test plan is confusing.

Not really, if you change the UI to show something like this.

[url=http://imageshack.u

fman wrote:You have another possibility: allow editing of executed test cases.
In this way you loose info about version, but can run build 2 against the
updated test cases.

But you'd loose the history of what was executed with a previous version of a test case.

fman wrote:I would be interested to know how other test management tools manage
the situation you have despicted.

If memory serves, Mercury/HP Quality Center does this but I'll see if I can find a copy the documentation.

e_chiappone · Post by **e_chiappone** » Wed Oct 24, 2007 11:36 pm

I understand the issue of not removing results when a test plan is updated, so that your results do not effectivly say that a certain test case passed, when actually a different version of the test case is what passed. However, it seems that the historic results should simply be noted that they were tested with a certain version, or moved to a different location, rather then eliminated.

Post by **fman** » Thu Oct 25, 2007 2:07 pm

Easy to say, but not so easy to implement without a big rethinking of TL architecture, => for now you must accept our tool limits.

Regards

e_chiappone · Post by **e_chiappone** » Thu Oct 25, 2007 3:30 pm

OK, I understand that my suggestion was way out of TestLink's architecture. So, accepting that updated test cases removes historic results, is there a good/easy way to update the test plan (or create a new one) with the updated test cases. Currently the only way I see of doing it is to create a new test plan (choosing to create it from the old one) then removing and re-adding each updated test case. This can be rather time consuming if a large number of changes have been made. There is the "LOCALIZE: href_newest_tcversions " function that lists the outdated test cases, but no way to update them. TestLink 1.6.3 had a function " Update modified Test Cases " that would provide the user a list of outdated test cases and allow them to check some/or all at once and update. Is there some similiar functionality in 1.7?

Sorry for paragraph, thanks for any help

Post by **fman** » Fri Oct 26, 2007 2:29 pm

NO there is not this feature.

1. do you want to help us to develop it. ?
2. please add this feature request into mantis, with as much detailed info as possible.

regards

davej409 · Post by **davej409** » Wed Dec 12, 2007 3:07 am

First off let me complement the TL team on their product, it is an excellent alternative to some of the commercial tools out there.

fman wrote:You have another possibility: allow editing of executed test cases.
In this way you loose info about version, but can run build 2 against the
updated test cases.

fman, how can one do this? IMHO, test case execution history is way more important then version control.

Thanks!

davej409 · Post by **davej409** » Wed Dec 12, 2007 3:36 am

fman wrote:I would be interested to know how other test management tools manage the situation you have despicted.

BTW, Quality Center allows for "on the fly" edits during execution runs and subsequent runs automatically pick up the newest version of a testcase.

There is no concept for multiple versions of a testcase as to what dealforme was eluding to. I can't speak for him but I don't think he actually wanted the ability to be able to run different versions of a testcase against the same build as separate instances...

davej409 · Post by **davej409** » Wed Dec 12, 2007 5:29 pm

I read the sticky posts and found out how to enable the editing of executed testcases in config.inc.php.

/** [Test case] */
// 1 -> user can edit executed tc versions
// 0 -> editing of executed tc versions is blocked. [STANDARD BEHAVIOUR]
$g_testcase_cfg->can_edit_executed=1;

Thanks!

rbflora · Post by **rbflora** » Thu Dec 13, 2007 4:28 pm

Thank`s davej you solve my problems , just a concern TestLink works correctly after you change parameter ??

Regards

Ricardo.

davej409 · Post by **davej409** » Thu Dec 13, 2007 9:12 pm

Yup. Works great! Just edit the config file and you can edit executed testcases.

bizob28 · Post by **bizob28** » Mon Dec 01, 2008 6:37 pm

Thanks davej, however I got to this point and looked for possible solutions. My problem now is that I have created a newer version of a test case, and edited the config file to allow editing of versions that have been executed. Now...I can edit versions of test cases that have been edited if a newer version does not exist. My real problem is I want to edit a test case version 1 but a version 2 exists, and with this configuration I cannot do so. Any thoughts?

updating test plan with new version of test cases

updating test plan with new version of test cases

does it work correctly?