We are quite impressed how capable TestLink is, and now we wonder how we can build up the basic structures to get our realities represented in TestLink as good as possible.
We have two product lines A and B. A has 2 products, B has 10. Both A and B have about 50 components.
Most of the components are only shared by the products of a product line, but some of them are used in product lines A and B.
Regarding the Test Projects - what's a good strategy to organize the product lines and the shared components?
Any product has to work on a variety of platforms (a bunch of browsers or operating systems and their variations, for instance W2k3 x86/x64 / W2k8 x86/x64 /Core/Cluster).
Many test cases are run several times per build, not only because of the platforms, but because the test cases have variations. The test case is basically the same, but run 2 times for RDP and ICA protocol, or with SSL and without SSL for instance. Can we handle variations like this without copying the test cases multiple times?
We would be very happy if there is somebody out there who has similar problems and could advice.
In the meantime, is there any "strategy documentation" we could check?
How to build up the basic structure?
Moderators: Amaradana, TurboPT, TL Developers
Re: How to build up the basic structure?
>>We have two product lines A and B. A has 2 products, B has 10.
>>Both A and B have about 50 components.
>>Most of the components are only shared by the products of a product line, but some of them are used in product lines A and B.
>>Regarding the Test Projects - what's a good strategy to organize the product lines and the shared components?
My suggestion, create one test project for each product => 2 + 10 => 12 test projects
Only sharing available is at SINGLE TEST CASE level (give a look to FAQ part of forum)
>> Any product has to work on a variety of platforms (a bunch of browsers or operating systems and their variations,
>> for instance W2k3 x86/x64 / W2k8 x86/x64 /Core/Cluster).
Here you can use TestLink Platforms
>> Many test cases are run several times per build, not only because of the platforms, but because the test cases have variations. The test >> case is basically
>> the same, but run 2 times for RDP and ICA protocol, or with SSL and without SSL for instance.
>> Can we handle variations like this without copying the test cases multiple times?
Using Custom Fields
>> In the meantime, is there any "strategy documentation" we could check?
Unfortunatelly no, I think this will be a good opportunity to create it if comunituny contribute.
Anyway I suggest you to browse different posts forum
At Last a favour: if you are happy with TL please spread the news:
1. add your company on forum
2. post a review on sourceforge
3. ask on jumpbox for a TL jumbox
4. same on TurnKeyLinux
>>Both A and B have about 50 components.
>>Most of the components are only shared by the products of a product line, but some of them are used in product lines A and B.
>>Regarding the Test Projects - what's a good strategy to organize the product lines and the shared components?
My suggestion, create one test project for each product => 2 + 10 => 12 test projects
Only sharing available is at SINGLE TEST CASE level (give a look to FAQ part of forum)
>> Any product has to work on a variety of platforms (a bunch of browsers or operating systems and their variations,
>> for instance W2k3 x86/x64 / W2k8 x86/x64 /Core/Cluster).
Here you can use TestLink Platforms
>> Many test cases are run several times per build, not only because of the platforms, but because the test cases have variations. The test >> case is basically
>> the same, but run 2 times for RDP and ICA protocol, or with SSL and without SSL for instance.
>> Can we handle variations like this without copying the test cases multiple times?
Using Custom Fields
>> In the meantime, is there any "strategy documentation" we could check?
Unfortunatelly no, I think this will be a good opportunity to create it if comunituny contribute.
Anyway I suggest you to browse different posts forum
At Last a favour: if you are happy with TL please spread the news:
1. add your company on forum
2. post a review on sourceforge
3. ask on jumpbox for a TL jumbox
4. same on TurnKeyLinux
Re: How to build up the basic structure?
Thank you, this helped a lot. Is somebody out there who could give us a short WebEx or something similar?
By the way, I asked for a jumpbox already, and I will post a review on sourceforge as soon as I know a little more about TestLink. (I don't like this one line yeah-great-stuff posts, because they are useless.)
By the way, I asked for a jumpbox already, and I will post a review on sourceforge as soon as I know a little more about TestLink. (I don't like this one line yeah-great-stuff posts, because they are useless.)
Re: How to build up the basic structure?
please contact:
testlink.helpe@gmail.com
to understand if an skype session with shared screen can be equivalent to a WebEx
testlink.helpe@gmail.com
to understand if an skype session with shared screen can be equivalent to a WebEx