Forum Discussion
Colin_McCrae
12 years agoCommunity Hero
Think I may have jumped the gun.
I thought all the enabled plugins were at project level. They're not. They an application setting.
So when I updated to v10.20, it switched on all the plugins I had switched off.
These seem to make a huge difference to performance.
Prior to using TestComplete, I used QTPro. Your approach to plugins and theirs is the opposite. With TC, everything is switched on by default. With QTPro, everything is off and you add in the plugins your test needs.
Not convinced having them all switched on by default is the best idea when they make this much difference to performance.
Or maybe the plugin settings could be stored at project level?
I'm re-running my 4hrs 20mins test now with nothing else changed except the plugin settings. I'll post back to see what difference they made but I think it's likely to be huge ...
And although this helps, it still doesn't explain the performance drop-off I saw when going from v10.0 to v10.10 & v10.20.
I didn't change any plugin settings when going from v10.0 to v10.10 and the test time did more than double. I only got the performance back by shutting down plugins.
So maybe there was a heavy duty plugin introduced at v10.10 which is hitting performance?
I didn't install any of the mobile testing modules when I updated ....
I thought all the enabled plugins were at project level. They're not. They an application setting.
So when I updated to v10.20, it switched on all the plugins I had switched off.
These seem to make a huge difference to performance.
Prior to using TestComplete, I used QTPro. Your approach to plugins and theirs is the opposite. With TC, everything is switched on by default. With QTPro, everything is off and you add in the plugins your test needs.
Not convinced having them all switched on by default is the best idea when they make this much difference to performance.
Or maybe the plugin settings could be stored at project level?
I'm re-running my 4hrs 20mins test now with nothing else changed except the plugin settings. I'll post back to see what difference they made but I think it's likely to be huge ...
And although this helps, it still doesn't explain the performance drop-off I saw when going from v10.0 to v10.10 & v10.20.
I didn't change any plugin settings when going from v10.0 to v10.10 and the test time did more than double. I only got the performance back by shutting down plugins.
So maybe there was a heavy duty plugin introduced at v10.10 which is hitting performance?
I didn't install any of the mobile testing modules when I updated ....