Add Test-cases from another "Test Project" to Test
Add Test-cases from another "Test Project" to Test
I have two Test projects namely X and Y.
I created a Test plan (Z) under X and added test cases from same project to it.
As per the user documentation section 5.3, it shall be possible to add test cases from another test-project Y to test plan Z.
Wondering how can it be achieved ?
thanks,
I created a Test plan (Z) under X and added test cases from same project to it.
As per the user documentation section 5.3, it shall be possible to add test cases from another test-project Y to test plan Z.
Wondering how can it be achieved ?
thanks,
-
- Advanced user
- Posts: 20
- Joined: Tue Oct 21, 2008 6:41 am
- Location: Bangalore, INDIA
- Contact:
I have installed version 1.7.4 and 1.8 beta 3 (in parallel). They are unaware of each other.
Download the user manual using the link
http://www.teamst.org/_tldoc/1.7/user_manual.pdf
The section 5.3 clearly states that "Data from multiple Test Projects can be added into one Test Plan"
could be possible that I am misinterpreting something.
Thanks for reply.
Download the user manual using the link
http://www.teamst.org/_tldoc/1.7/user_manual.pdf
The section 5.3 clearly states that "Data from multiple Test Projects can be added into one Test Plan"
could be possible that I am misinterpreting something.
Thanks for reply.
-
- Advanced user
- Posts: 20
- Joined: Tue Oct 21, 2008 6:41 am
- Location: Bangalore, INDIA
- Contact:
I downloaded the User manual for Testlink 1.7.
If you lookup '5.3', you'll see this:
----------------------------------------
5.3 Populating Test Plan - adding Test Cases
Data from multiple Test Projects can be added into one Test Plan. Test Specification data can
be filtered by keywords (adjusted in navigation pane).
----------------------------------------
That is the confusing bit.
Is this possible with 1.8 ?
Thanks
Raj
If you lookup '5.3', you'll see this:
----------------------------------------
5.3 Populating Test Plan - adding Test Cases
Data from multiple Test Projects can be added into one Test Plan. Test Specification data can
be filtered by keywords (adjusted in navigation pane).
----------------------------------------
That is the confusing bit.
Is this possible with 1.8 ?
Thanks
Raj
Participate and help people become better testers
http://www.softwaretestingconcepts.com
http://www.softwaretestingconcepts.com
I can see two issues directly related to this issue.
http://www.testlink.org/mantis/view.php?id=867
and
http://www.testlink.org/mantis/view.php?id=758
both are closed ("wont fix" and "no change required").
I can try to implement the solution suggested in 867, and see what happens.
will let you know.
I hope you meant these two issues, or there were some other as well.
thanks for reply.
http://www.testlink.org/mantis/view.php?id=867
and
http://www.testlink.org/mantis/view.php?id=758
both are closed ("wont fix" and "no change required").
I can try to implement the solution suggested in 867, and see what happens.
will let you know.
I hope you meant these two issues, or there were some other as well.
thanks for reply.
simple solution for complex problems always means wrong results.
We have choose time ago to maintain test plans as test project children, and one children can not have two different parent.
You are missing many aspects of TL, like save execution results, reporting, etc.
We will reconsider in future, how to reimplement this feature, but is not simple matter of adding testproject id to test plan table.
Issue is wide enough that is not possible to be discussed via forum.
This issue has not high priority (at least today) for future releases.
We have choose time ago to maintain test plans as test project children, and one children can not have two different parent.
You are missing many aspects of TL, like save execution results, reporting, etc.
We will reconsider in future, how to reimplement this feature, but is not simple matter of adding testproject id to test plan table.
Issue is wide enough that is not possible to be discussed via forum.
This issue has not high priority (at least today) for future releases.
Totally understandable; and agree with every bit of your comments.
In companies (feks like ours) where they have multiple products; its quite often that the products are related/dependent to each other (behind the scenes); they share some common features/components even DB.
Like you said, its a nice to have feature, and I agree; shouldn't be high on priority list.
Thanks for explanation anyway.
In companies (feks like ours) where they have multiple products; its quite often that the products are related/dependent to each other (behind the scenes); they share some common features/components even DB.
Like you said, its a nice to have feature, and I agree; shouldn't be high on priority list.
Thanks for explanation anyway.
would really like this feature
PLEASE correct the manual. This was a key needed feature, and we would also use it to create reports across all projects. We will probably now have to clump projects together and this makes it impossible to link to our bug-tracking. I installed based on the manual, and now we have to re-think it all. otherwise, thanks 

I apologize for confusing you. Manual for 1.7 is not clear. It is described better in manual for 1.8 version.
I think about possibility to share data your way. Maybe some master report based on data from more Test Plans could be solution acceptable by DEV team better than shared Test Plans. Do you have idea how it should work? How to say which data will be in such report?
In our company Integration test team has own Test specification so we have not this problem.
I think about possibility to share data your way. Maybe some master report based on data from more Test Plans could be solution acceptable by DEV team better than shared Test Plans. Do you have idea how it should work? How to say which data will be in such report?
In our company Integration test team has own Test specification so we have not this problem.