There needs to be some way to easily customize the settings within TestExecute without having to login to every machine that has TestExecute installed on it and manually configuring it. Either in...
Dmitry_Nikolaev Below are the three items that we have to configure on every installation. The other issue we have found now that we have the configuration automated is that TestExecute fails with a exit code of 127 when launched via Jenkins if it hasn't been launched previously under the same USER profile manually. We are still looking into the exact cause of this, but we still do not have everything fully automated at this time because of this issue.
- Setting the Java bridge configuration
- Disabling the "Send feature usage data to help improve TestExecute" option
- Our company is very sensitive to sending any data out of the company.
- Disable "Check for updates at startup".
- Automated tests through Jenkins will fail if this is enabled and an update is detected at the time TestExecute launches.