Forum Discussion
I'm not sure what your question is. Could you give us a more detailed example?
- Manfred_F9 years agoRegular Contributor
Ok, I give You 2.
Ex.1: I do use a dynamically changed commandline for my testedApp object.
This results in a request to save the changes as soon as I Close TC. I don't want this!
Ex.2: During Test run, I Change options.Run.Timeout dynamically.
This results in a request to save the changes as soon as I Close TC. I don't want this!
- Marsha_R9 years agoModerator
Your dynamic change isn't the only thing that is causing that message to appear. Your test log is changing and that will also prompt a save when you close TC.
If you want to skip all the TC messages, perhaps running your test in TestExecute is a better option. Once you have your test behaving the way you like, you can run it from TE and you'll never see the main UI. Would that help?
- Manfred_F9 years agoRegular Contributor
Well, in my Installation of TC, the TestLog doesn't lead to a storage request on application Close, but changing commandline Parameters in testedapps does.
TestExecute does not help, as it does the same storage request on Close.
Related Content
- 5 years ago
Recent Discussions
- 3 days ago
- 3 days ago
- 6 days ago