Large project? Recording Region Checkpoint takes 14 seconds for dialog to appear
I'm using TC v9.30, but v9.20 had the same issue.
My project has grown to about 560 KeywordTests with about 780 Regions in Stores, but that doesn't seem to me like it should be too large. The suite runs in about 3 hours.
When recording a new test, I select Region Checkpoint and it takes about 14 seconds before the checkpoint dialog appears. Note that if I do a Property Checkpoint, the dialog appears immdediately.
As a test, I created a new Project in my Project Suite. When selecting the Region Checkpoint option in that project the dialog appears immediately. I merged the NameMapping from the large project into the new empty one, and it is still immediate, so the size of my NameMapping file doesn't seem to be the problem.
My best guess is that the slowness is due to the number of Regions which has climbed over 780 and will continue to grow.
I don't know what to do!
If I split my tests into multiple Projects within the Suite, then I get back to a problem that I had a year or two ago. That is, trying to share scripts and KeywordTests between the Projects is a real pain. I found it impossible to update a shared script or KeywordTest without either getting warnings about the item "changing" outside of TestComplete, or, the item would somehow diverge and not be the same for every project.
Every KeywordTest calls at least 2 other KeywordTests: the setup and teardown for the testedApp.
What do people do?
What could the RegionCheckpoint possibly be doing to take so long?
Any suggestions?
My project has grown to about 560 KeywordTests with about 780 Regions in Stores, but that doesn't seem to me like it should be too large. The suite runs in about 3 hours.
When recording a new test, I select Region Checkpoint and it takes about 14 seconds before the checkpoint dialog appears. Note that if I do a Property Checkpoint, the dialog appears immdediately.
As a test, I created a new Project in my Project Suite. When selecting the Region Checkpoint option in that project the dialog appears immediately. I merged the NameMapping from the large project into the new empty one, and it is still immediate, so the size of my NameMapping file doesn't seem to be the problem.
My best guess is that the slowness is due to the number of Regions which has climbed over 780 and will continue to grow.
I don't know what to do!
If I split my tests into multiple Projects within the Suite, then I get back to a problem that I had a year or two ago. That is, trying to share scripts and KeywordTests between the Projects is a real pain. I found it impossible to update a shared script or KeywordTest without either getting warnings about the item "changing" outside of TestComplete, or, the item would somehow diverge and not be the same for every project.
Every KeywordTest calls at least 2 other KeywordTests: the setup and teardown for the testedApp.
What do people do?
What could the RegionCheckpoint possibly be doing to take so long?
Any suggestions?
