Hi,
I'm wondering about your experiences in managing test projects with Testlink.
How many test-cases, test-results, builds etc. can you manage within Testlink?
We tried Testlink to manage our test results of our nightly tests, but unfortunately the database queries of Testlink have a too low performance.
We have one test project, with one execution plan "nightly" and we import the test results of our builds into that execution plan. We have two builds per day with about 3000 test results. So we import 6000 test results per day. After a week we want to compare the test results, if we see tests which are failing, but we can't use the GUI, because the performance is simply too bad (I saw SQL select statements with a lot of joins).
Are there any experiences or any hints about optimizing the result query?
Thanks in advance!
Regards,
Martin
Size of project - number of results - optimization hints
Moderators: Amaradana, TurboPT, TL Developers
I agree at some point of time, there will be an performance issue, as i am also facing same problem, we had 1000 test cases and we executed for almost 14 build i guess.. in some page it is slow. Rather than asking in the forum, can you optimize for us?
My Next step: I am trying to migrate to SQL 2003, and check the performace with IIS, if i am still facing the problem next step would be indexing.
My Next step: I am trying to migrate to SQL 2003, and check the performace with IIS, if i am still facing the problem next step would be indexing.
Thank you please post your observations. So that they will be useful for the other users also. I am trying IIS only becoase to know how the performance/anything else, whether to see which wil be good server, i used wamp +mysql and Xampp +mysql, in this two i suggest anyone to use Xampp+mysql among these two combinations.