Build-focussed approach in Testlink ?

[renaud2]

Dear Testlink Developers and Users

We are a SW company developing for Home Gateway and Set Top Boxes and using testlink with version 1.9.4 as test execution and testcase management tool.
We use the Testplatforms for our different Hardware versions on which we execute many testplans (one testplan is usually covering the tests of one feature of the SW, some testcases being common others specific to the platform) testing different SW versions (builds).

I am unfortunately still not a very advanced Testlink user which is why I address my questions here. I apologize in advance if I misunderstood anything.

As far as the very little I understand the testlink architecture, there are some things that I am missing or maybe only missing the way to do them.
The main topic I am missing is an overall view (test execution report) of the different tests performed on one build.
I am only able to get a test report per Testplan, but in order to validate in all its extent the SW version we are testing, we need an overall test execution report (as well as requirement coverage report for instance) in order to know which testplans have been executed on the one build we are planning to deliver to our client and with wich result.
In the same idea, I don't really understand why the testlink architecture forces the user to create a build per testplan. Did we misundestand the concept of test project and testplan in Testlink ?
As I was stating, we need to run many testplans in order to validate one Build, so why is a build specific to a testplan (on the contrary to platforms) ?


Another item I have searched for is the need to share testcases between different testprojects for many of them are identical from one project to the next (one project being one Hardware with many different versions).

I thank you very much in advance and would be very grateful for your answer that shall help me to better understand this very useful tool.
Best Regards,
Renaud

[fman]

>> I don't really understand why the testlink architecture forces the user to create a build per testplan. Did we misundestand the concept of test project and testplan in Testlink ?
is a design choice, that will not be changed.

>> As I was stating, we need to run many testplans in order to validate one Build, so why is a build specific to a testplan (on the contrary to platforms) ?
design choice.

>> Another item I have searched for is the need to share testcases between different testprojects for many of them are identical from one project to the next (one project being one >> Hardware with many different versions).
We ahve already explained that search can be done using ghost feature
You need to refine your search and also use the right approach on post: ONE POST ONE TOPIC, thing you have not done here.

using 1.9.4 is a great error because you are missing lots of new features. what features? read README of each testlink release for this info

[renaud2]

Thank you very much for your answers fman. I apologize for my misrespect of the forum rules.

If I may ask another question, from the design choice, if I understand correctly, there is no way to get a report per build, is there?

[fman]

answer is again
using 1.9.4 is a great error because you are missing lots of new features. what features? read README of each testlink release for this info
Give a look to demo.testlink.org