TestLink

We are using TestLink 1.70 and are generally happy with the tool. As others have stated, there are performance issues when you have large amounts of data. We have 10,500+ test cases with a team of 10 QA Engineers actively updating and executing test cases all day long. We did notice some improvement...

We are using TestLink as the main engine that drives both our test case management and automation infrastructure. We have integrated our automation framework into Testlink so that we have the following functionality: 1. Test case documentation and automation scripts in one app 2. Selection of automa...

It would be a nice feature to be able to link a defect report to a test case. Most defect tracking systems support clicking on a hyperlink which will take you directly to a defect report. If you could paste in a hyperlink into the test case upon execution, it would allow you to easily link back to t...

I was wondering if it would be possible to add some additional fields to track the state of the test case development. For example, we usually have our QA Leads review and approve all test cases which have been created by the team. This ensure that we have uniformity in terms of writing style, level...

It would be nice to support the concept of phases so that you could tie the report of test case execution to specific phases of a project. Today, you can tie test cases to a specific test plan but that is quite limited since you may want to track test execution based upon specific criteria such as n...

Thanks for the help! We are really happy with TestLink and are looking forward to 1.7.

There are a number of enhancements that I would like to see in 1.7. I was curious if these are being considered for the next release. 1. Better sorting of test cases. The current method of sorting is very painful. Trying to insert a new test case between two existing test cases when you have over 10...

I noticed that if you have a lot of components defined in your tree, the performance is quite slow. We currently have about 80 components and notice that it takes about 30 seconds to display the tree. Is this something that will be given more attention in 1.7? We are planning on rolling this out to ...