using TC properties dynamically
my test requires to use TC properties dynamically, e.g. TestedApp.Params.ActiveParams.CommandLineParameters. After using the generated value, the Default value is reset. This leaves me with a st...
Forum Discussion
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!
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?
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.
Okay, I see.
I don't see how you would do it without a Save. You're asking TC to update settings without saving them. I know it's extra steps, but are you having an issue with the Close? Maybe I can help with that.
Well, if I knew how to do a save, this would solve my issue.
What I aim at is to run TE silently, controlled by a Scheduler. Therefore I don't want any GUI Actions like message boxes.
Concerning the TestedApps object, I will apply a Workaround using something like vbScript shellexecute instead of applicaiton.run, so I don't have to Change the testedapps object.
