Forum Discussion
There isn't that I know of... TestExecute options are stored in the user profile of whoever is logged in at the time. So, even if you configure it on the machine, if you log off and log in as a different user, you will need to configure again.
I suppose (and this is untested) that you might be able to "fix" this by having the user that you use for test execution use a "Roaming" profile in your windows AD... that way, no matter what machine they log into, they'll have the same configuration/setup. This is COMPLETELY untested so it's just presented as a theory but it's worth a try.
This is very disappointing to hear. A tool like this should be configurable without having to touch every workstation you install it on. We have 10 TestExecute floating licenses and due to the how fluid the testing environment is, we have to come up with a solution.
While your proposal would definitely work in theory, I would prefer not to go down that path as it would change our standard desktop configuration and potentially invalidate some of our testing as a result.
I did see that the tcsettings.xml file exists in the user profile. However I also saw that there was a "defaulttcsettings.xml" file in the installation folder for TestExecute. Unfortunately it uses a bunch of GUID type strings and is not readable as far as determining what settings are what. I was hoping that this file might be what it sounds like and are the settings that ultimately get copied over to the user profile once it is logged in and created. Unfortunately like I said, it is very difficult to interpret the way it has been written.
- tristaanogre8 years agoEsteemed Contributor
I can't imagine that you're the first person to request such a thing... You might want to consider contacting SmartBear support directly.
https://support.smartbear.com/message/?prod=TestComplete- DavidE8 years agoContributor
I will open a ticket with SmartBear on this. Once I hear back, I will share the response here for future reference, because as you say, I am sure I am not the first person to have this issue.
Thanks,
David Evans