Very slow test startup
Hi everyone, We have a TestComplete (v8.6) project suite with over 700 automated tests. We are using TestExecute to play these tests back. The issue is that when the tests are executed, i...
Forum Discussion
Thank you guys both for your responses.
Paul, does this compilation happen only once during the test run or is it before every test? I am using COM automation to drive TestExecute. I only open the project suite before the first test then TFS takes over as far as telling it which scripts to run. The delay occurs between every test in the run though, so I'm curious if it's trying to compile the entire project before every test...?
Our scripts vary widely in length depending on the test, but just looking at the metrics... we have 770 script units with 47,454 lines of code so we're averaging about 59 lines per script.
Is the number of scripts per PROJECT (not project SUITE) the main issue? Because I could technically split the scripts into separate projects within the same project suite, but that will be a huge undertaking so I want to make sure it will make a significant difference before I attempt it.
Robert, we are using TFS as our primary "framework" for writing tests. Our QA testers write test cases in TFS, then we script them (using one script unit per case to keep them separate) and associate the script back to the test case. When playing the tests back, I have written a test "harness" that drives TestExecute to execute each test similar to a unit test. We have written a library of functions that are used repeatedly, but we have to use TFS because that is what our department uses and it allows us to keep a history for each test case.
Are there any plans to improve performance in larger projects like this? We purchased 5 licenses of TestComplete Enterprise for this very reason, because we were told that there is no limit to the number of script units a project may contain. While this is technically true, a performance limit of 50 scripts per project for testing a huge application like we are is a major cause of concern right now.
Paul, does this compilation happen only once during the test run or is it before every test? I am using COM automation to drive TestExecute. I only open the project suite before the first test then TFS takes over as far as telling it which scripts to run. The delay occurs between every test in the run though, so I'm curious if it's trying to compile the entire project before every test...?
Our scripts vary widely in length depending on the test, but just looking at the metrics... we have 770 script units with 47,454 lines of code so we're averaging about 59 lines per script.
Is the number of scripts per PROJECT (not project SUITE) the main issue? Because I could technically split the scripts into separate projects within the same project suite, but that will be a huge undertaking so I want to make sure it will make a significant difference before I attempt it.
Robert, we are using TFS as our primary "framework" for writing tests. Our QA testers write test cases in TFS, then we script them (using one script unit per case to keep them separate) and associate the script back to the test case. When playing the tests back, I have written a test "harness" that drives TestExecute to execute each test similar to a unit test. We have written a library of functions that are used repeatedly, but we have to use TFS because that is what our department uses and it allows us to keep a history for each test case.
Are there any plans to improve performance in larger projects like this? We purchased 5 licenses of TestComplete Enterprise for this very reason, because we were told that there is no limit to the number of script units a project may contain. While this is technically true, a performance limit of 50 scripts per project for testing a huge application like we are is a major cause of concern right now.
