Test cases from two different projects
Test cases from two different projects
Is it possible to have a test plan that has test cases from 2 different projects?
For example, in my department we have many different systems that use common features. With our current TestLink (1.04 - old!) we have test plans that include test cases from different projects. We have projects that have test cases specific to that system then a project that has common test cases for all systems. When we get a new build we create a test plan with test cases from the project of the particular system under test and test cases from a project that holds all our common test cases.
I cannot see how to do this on TL 1.7. Is it possible?
Paul
For example, in my department we have many different systems that use common features. With our current TestLink (1.04 - old!) we have test plans that include test cases from different projects. We have projects that have test cases specific to that system then a project that has common test cases for all systems. When we get a new build we create a test plan with test cases from the project of the particular system under test and test cases from a project that holds all our common test cases.
I cannot see how to do this on TL 1.7. Is it possible?
Paul
ON 1.6 and 1.7 testplans are related one to one to test projects.
ON 1.6 there was possibility to avoid filter testplan by testprojects.
ON 1.7 we have disabled this feature, and we are in a process of rethinking
it .
If you think is useful report a NEW FEATURE request on mantis, with as much details as possible.
ON 1.6 there was possibility to avoid filter testplan by testprojects.
ON 1.7 we have disabled this feature, and we are in a process of rethinking
it .
If you think is useful report a NEW FEATURE request on mantis, with as much details as possible.
Having test plan including test cases from many projects would be a VERY useful feature.
We have a similar scenario - one COMMON project for test cases used across all specific projects, and different projects for different products. Right now we create test plans for specific projects and also corresponding test plans in COMMON project for the generic test cases.
Having the ability to include COMMON test cases in product specific test plans would simplify a lot of things. Included test cases could behave the same way they do now (after exexuted->block editing) and access to them could be based user priviliges specific to project (so a user that can create test plan in a "specific" project would be able to add test cases only from projects to which he/she has access rights).
Would you consider enabling such functionality? I don't think it would be that difficult (maybe apart from the access rights part). Should I puta feature request to Manits?
We have a similar scenario - one COMMON project for test cases used across all specific projects, and different projects for different products. Right now we create test plans for specific projects and also corresponding test plans in COMMON project for the generic test cases.
Having the ability to include COMMON test cases in product specific test plans would simplify a lot of things. Included test cases could behave the same way they do now (after exexuted->block editing) and access to them could be based user priviliges specific to project (so a user that can create test plan in a "specific" project would be able to add test cases only from projects to which he/she has access rights).
Would you consider enabling such functionality? I don't think it would be that difficult (maybe apart from the access rights part). Should I puta feature request to Manits?
>>Would you consider enabling such functionality? I don't think it would be >>that difficult (maybe apart from the access rights part). Should I puta >>feature request to Manits?
do not report issue, because we will reject it.
We have decided time ago this is a feature we do not want on TL.
In other hand due to new architecture on 1.7 and up, where test cases are really linked and NOT Copied to test plans implementation is more difficult that you can think.
I'm sorry
do not report issue, because we will reject it.
We have decided time ago this is a feature we do not want on TL.
In other hand due to new architecture on 1.7 and up, where test cases are really linked and NOT Copied to test plans implementation is more difficult that you can think.
I'm sorry
-
- TestLink user
- Posts: 9
- Joined: Sat Dec 22, 2007 10:01 am
-
- Advanced user
- Posts: 33
- Joined: Tue Jan 20, 2009 4:57 pm
- Location: Las Vegas
- Contact:
1.8 RC3 - move/copy test case/suite
Hello,
in regards to this topic I was wondering if the move/copy feature of test cases within the parent test project has evolved yet to include the movement or coping of test cases and suites across projects?
The work around for now has been to export the test suites and import into a new project. Our testing contains very similar test cases (if not the exact same ones) as our AUT remains the same only different installations of it per client. So, we reuse the same test cases across most of our projects. A more fluent way to get copies of test cases rather than export/import would be very nice.
Thank you!
in regards to this topic I was wondering if the move/copy feature of test cases within the parent test project has evolved yet to include the movement or coping of test cases and suites across projects?
The work around for now has been to export the test suites and import into a new project. Our testing contains very similar test cases (if not the exact same ones) as our AUT remains the same only different installations of it per client. So, we reuse the same test cases across most of our projects. A more fluent way to get copies of test cases rather than export/import would be very nice.
Thank you!
-
- Advanced user
- Posts: 33
- Joined: Tue Jan 20, 2009 4:57 pm
- Location: Las Vegas
- Contact:
Thank you!
Indeed, this feature would be very nice. I appreciate the consideration, please let me know if there is anything I can do to help.
I already posted request http://www.testlink.org/mantis/view.php?id=2095. You can monitor it, state your ideas or the best contribute 
