|Anonymous | Login | Signup for a new account||2019-10-17 03:55 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0006390||TestLink||Test Execute||public||2014-06-15 05:54||2014-07-28 20:33|
|Product Version||1.9.10 (2014 Q1 - bug fixing)|
|Fixed in Version||1.9.11 (2014 Q2 - bug fixing)|
|Summary||0006390: Tree is slow to load when user clicks on Test Execution.|
|Description||I am using TL 1.9.10. It has only 1 Test Plan with around 700 Test Cases. It is observed that when user/tester clicks on "Test Execution" then the page is slow to load, somewhere around 2 mins. I believe it is do with preparing and rendering the tree on the left panel. But the same is not observed on "Test Specification". I ran a profiler (xdebug with webgrind) and it seems to point at "treeMenu.inc.php" file "line:887" where the function recursively calls itself to form the execution tree. |
|Steps To Reproduce||Click on Test Execution.|
|Tags||No tags attached.|
|QA Team - Task Workflow Status||TBD|
|Attached Files|| big_tree.testproject-deep.xml.gz [^] (87,343 bytes) 2014-06-15 09:20|
linkedItems_TPLAN_700.xml.gz [^] (8,203 bytes) 2014-06-15 09:26
linkedItems_TPLAN_400.xml.gz [^] (5,198 bytes) 2014-06-15 09:26
bit_tree_model3.testproject-deep.xml.gz [^] (260,551 bytes) 2014-06-15 10:02
testlink.zip [^] (86,328 bytes) 2014-06-15 14:26
bit_tree_model3_V2.testproject-deep.xml.gz [^] (267,658 bytes) 2014-06-15 15:46
Screenshot 2014-06-15 22.50.58.jpg [^] (992,138 bytes) 2014-06-15 17:21
1. Test project size (amount of test suites and test cases) has impact on performance.
2. test project structure => How many Test Suites and how many levels of test suites (i.e. tree depth) also.
Tree structure on DB is the simplest one, then in order to be walked, recursive approach is needed.
It will be important to have a dump of your DB in order to do some tests.
edited on: 2014-06-15 09:24
I've just created on demo.testlink.org a test project: big_tree
I've attached here the XML to recreated this test project.
This way we can have a common playground, at least in structure.
Also exported test plan with 400 test cases.
In this way We can do tests on same hardware. use admin/admin to login
|bit_tree_model3.testproject-deep.xml.gz => 2862 test cases inside|
You can change on demo site and add as much test cases as you want in order to understand if your structure affects performance
Demo is ubunti with TESTLINK & MYSQL on same host, may be this can affect something.
Juste create a test suite ALFA that have test suites inside with more than 100 test cases => no issues
You can give a look
These errors IMHO generate more work than needed.
Do you think you can try to create a SANDBOX using latest code from gitorious, where I think these errors has been fixed ?
You need to create a NEW DB using your current DB as starting point, and then apply sql scripts to add new table used to hold execution notes & results at test step level
Tried with "TestLink Dev1.9.10(El D1eG0)" from Git repo "testlink-ga-testlink-code-e29b417beed04df8882872c88dc9e9e6eb5aed9a" on my Ubuntu VM running MySQL and the same tree structure is loading fine.
Please suggest how we can merge the fix as a patch from Dev branch to Stable 1.9.10 Prague branch.
I have replaced below files on my TL source tree and this seems to solve the performance issue but there are few unpleasant warnings in the log.
Please suggest/provide a confirmed official patch.
>> Please suggest/provide a confirmed official patch.
regarding providing official patch: this is not the way things works here.
There are no intermediate patches: you have two options:
a) get latest code from gitorious (it will become next stable release) and use it applying changes to db if needed
b) use specific commit on gitorious, doing the merge for yourself
|2014-06-15 05:54||Jasmeet||New Issue|
|2014-06-15 09:04||fman||Note Added: 0021113|
|2014-06-15 09:04||fman||Assigned To||=> fman|
|2014-06-15 09:04||fman||Status||new => feedback|
|2014-06-15 09:17||fman||Note Added: 0021114|
|2014-06-15 09:20||fman||File Added: big_tree.testproject-deep.xml.gz|
|2014-06-15 09:21||fman||Note Edited: 0021114||View Revisions|
|2014-06-15 09:24||fman||Note Edited: 0021114||View Revisions|
|2014-06-15 09:26||fman||File Added: linkedItems_TPLAN_700.xml.gz|
|2014-06-15 09:26||fman||File Added: linkedItems_TPLAN_400.xml.gz|
|2014-06-15 10:02||fman||File Added: bit_tree_model3.testproject-deep.xml.gz|
|2014-06-15 10:02||fman||Note Added: 0021115|
|2014-06-15 13:56||Jasmeet||Status||feedback => assigned|
|2014-06-15 14:26||Jasmeet||File Added: testlink.zip|
|2014-06-15 15:17||fman||Note Added: 0021119|
|2014-06-15 15:45||fman||Note Added: 0021120|
|2014-06-15 15:46||fman||File Added: bit_tree_model3_V2.testproject-deep.xml.gz|
|2014-06-15 17:21||Jasmeet||File Added: Screenshot 2014-06-15 22.50.58.jpg|
|2014-06-15 17:33||fman||Note Added: 0021123|
|2014-06-16 12:10||Jasmeet||Note Added: 0021127|
|2014-06-16 12:10||Jasmeet||Note View State: 0021127: private|
|2014-06-16 12:11||Jasmeet||Note View State: 0021127: public|
|2014-06-16 14:49||Jasmeet||Note Added: 0021129|
|2014-06-17 21:30||fman||Note Added: 0021134|
|2014-06-17 21:31||fman||QA Team - Task Workflow Status||=> TBD|
|2014-06-17 21:31||fman||Status||assigned => resolved|
|2014-06-17 21:31||fman||Fixed in Version||=> 1.9.11 (2014 Q2 - bug fixing)|
|2014-06-17 21:31||fman||Resolution||open => fixed|
|2014-07-28 20:33||fman||Status||resolved => closed|
|Copyright © 2000 - 2019 MantisBT Team|