Maximum number of test cases?

Ask community to help.

Moderators: Amaradana, TurboPT, TL Developers

Post Reply
lavaletl
TestLink user
Posts: 2
Joined: Mon Jun 09, 2014 6:32 pm

Maximum number of test cases?

Post by lavaletl »

Hi everyone!

My company is thinking about using TestLink in quite large projects (number of test cases may become several K), but we would like to know more about other's experiences in large projects first.

Does anyone have experience with a large number of test cases (for one project) in TestLink? Is there a recommended maximum number of test cases?

Thank you for your answers :) !
lavaletl
TestLink user
Posts: 2
Joined: Mon Jun 09, 2014 6:32 pm

Re: Maximum number of test cases?

Post by lavaletl »

Somebody has an answer? No?
fman
Member of TestLink Community
Posts: 3106
Joined: Tue Nov 15, 2005 7:19 am

Re: Maximum number of test cases?

Post by fman »

>> several K?
1? 2? 10? 100? => no data provided

matter of fact:
if test spec tree is too deep (i.e. organized with test suite nested to 7 or more levels) this will impact on building test execution tree.
IMHO amount of test cases on a test project has to be less than 5K (anyway who can manage 5K test case manually?).
If you have more => create more test projects.
Issue: reports are always at test project levels.
rbryant
TestLink user
Posts: 2
Joined: Sat Jun 21, 2014 8:02 am

Re: Maximum number of test cases?

Post by rbryant »

Currently, the largest we have is 36K+ testcases in 1 project however the performance is lacking in many areas for something of this size. It would be very useful for a tool like this to keep information of this size and larger. Many of our Automated tests have been modified to create XML so we can upload the test to testlink. Our manager likes to see the information in detail and can use the numbers for quality certification.
fman
Member of TestLink Community
Posts: 3106
Joined: Tue Nov 15, 2005 7:19 am

Re: Maximum number of test cases?

Post by fman »

>> however the performance is lacking in many areas for something of this size
details of affected areas is needed

Performance is affected by Test Spec tree organization: i.e. if you have a complex organization of test suites that contains other test suites, and more test suites
(tree deep level) this is going to have impact on TREE BUILDING when

1. you use FILTERING ON TEST SPECS (no more tree lazy loading can be used)
2. TEST PLAN NAVIGATION (tree is building walking from leaves (test cases) to root)

DB Schema can not be changed in order to try to get better performace due to high amout of rework and testing.
Solution is to use to use a different structure (test plans with not more that 3K test cases, or may be 10K)
But in anycase this is a process of trial and error
Post Reply