Forum Discussion
Just as a note, those settings are available within the Project Suite editor in the TestComplete workspace itself. When you make those changes in the Project Suite, they are saved within the Project Suite. Once set, you shouldn't need to change them via code.
Think of them as compiler settings when compiling an application. Once the application is compiled and built out to the EXE, you can't very well go back into that application and change up those things that were applied by the compiler. In order to make such changes, it would need to be re-compiled. Once a project has started running, it can be considered to be "compiled" so anything that alters that workflow of the test project are "off limits" at run time.
Thank you all for the information.
But will be helpful if provisioned to update via code also.
- tristaanogre8 years agoEsteemed Contributor
As mentioned, that would not make sense. The project properties that you mention are, for lack of a better term, "compiled" when the test is started. Therefore, they are fixed. The reason they are read-only is because it doesn't make sense to change them mid test. If you want a project to stop, you can use Runner.Halt in code to stop any project, any time. If you use proper exception handling logic in your project (try/catch/finally), you can trigger your project halts as needed.
If you do want to make the feature request, you may do so at https://community.smartbear.com/t5/TestComplete-Feature-Requests/idb-p/TestXCompleteFeatureRequests however I'm not entirely certain it will be something that SmartBear will pick up for development... not being an employee, that's just my opinion but it seems unlikely.