Linked-Copies of Test Cases

[NateAZ]

Is it possible to create a linked-copies of a test-case?

I don't want to create a copy of a test-case, but would actually like to define a test-case once and then have the ability to store it in multiple locations. This would be useful in the case where I have a standard test defined and then have "folders" created for different products that I want to conduct that test against - in other words the product I am testing will be tested against other products (one to many). Creating duplicate tests it not efficient from a maintenance perspective. Changes to the root test-case would then be propogated down to the linked test-cases.

If this capability exists I would love to know how/where to implement it. If not, then how would one go about requesting this feature in a future release?

[Unhandled]

Sound like the exact purpose of a "Test Plan". Can you not create separate Test Plan for each "different products that I want to conduct that test against"?

Also look into Platforms (new in version 1.9.x). Perhaps a different platform for each different product.

[ibreestraat]

Question for NateAZ: Do you have already a workable solution for it because I have the same problem and working with platforms is no option for me because we also have to test on different platforms.

[fman]

give a look to mantis and new FAQ section on forum

[NateAZ]

Sorry for the delay guys, I didn't get any notifications of responses.

The answer is NO, I was not able to solve this efficiently.

In my case I am testing a product that abides by a technology standard (an internationally accepted set of interfaces). As part of my test plan I conduct interoperability tests with other products. I have test-cases that apply to each of those other products. Unfortunately, my solution was to copy/paste the test-cases, e.g.

[_coreTestCases-copy-doNotUseDirectly]
- test case 1
- test case 2
[otherApplication1]
- test case 1
- test case 2
[otherApplication2]
- test case 1
- test case 2

Like I said, it's not efficient, it's not what I wanted, it does require a lot of maintenance, but it works. I hope that helps somebody.

It sure would be nice to be able to create a linked test-case!

[fman]

Please explain what are the problems with solution detailed on FAQ. (is not clear if you have cheched it)
Please remember also that forum is not intended for feature request, but instead Mantis is the place.
Mantis is not the place for asnwers or helps regarding how to use TL.
in any case reuse between test project, has lots of side effects due to additional items like custom fields, keywords, requirements, user visibility due to test plan and/or test project rights, etc and is a feature we are very reluctant to add due to incredible amount of side effects.

[kob]

Sorry for the delay guys, I didn't get any notifications of responses.

The answer is NO, I was not able to solve this efficiently.

In my case I am testing a product that abides by a technology standard (an internationally accepted set of interfaces). As part of my test plan I conduct interoperability tests with other products. I have test-cases that apply to each of those other products. Unfortunately, my solution was to copy/paste the test-cases, e.g.

[_coreTestCases-copy-doNotUseDirectly]
- test case 1
- test case 2
[otherApplication1]
- test case 1
- test case 2
[otherApplication2]
- test case 1
- test case 2

Like I said, it's not efficient, it's not what I wanted, it does require a lot of maintenance, but it works. I hope that helps somebody.

It sure would be nice to be able to create a linked test-case!

Why don't you use testplans for this as said before ?
You define the testcases once.
- test case 1
- test case 2

Then create a testplan otherApplication1 and otherApplication2 to which you assign the testcases. It even allows you to work with different versions of testcases between the different testplans if needed.
I've got a simular problem as you have and solved it this way, so far I haven't found any other free tool supporting this properly.

For me, a project in Testlink is a "container" to hold the testcases, a Testplan in Testlink is a container to hold the testcases I need to execute for a specific product (=> so this is the actual project).
If needed work with platforms or custom keywords to differentiate between different devices.
Example: device under test is DEVICE A, you need interop tests against DEVICE B and C.
You have a testcase: interop1
You have platforms: DEVICE A, DEVICE B, DEVICE C
You have a testplan DEVICE A containing testcase interop1 mapped to platforms DEVICE B and DEVICE C.

If you need to test a new release of DEVICE C.
You already have testcase interop1
You already have the platforms: DEVICE A, DEVICE B, DEVICE C
You create a testplan DEVICE C containing testcase interop1 mapped to platforms DEVICE A and DEVICE B.