using TC properties dynamically

Question

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 storage request, e.g. for testedApps.

Is it possible to somehow reset the "dirty"-flag in TC? Or can I just do a SAVE (I'd prefer the former..)?

The effect Shows for testedApps, for Options and for ODT.Data.

tristaanogre · Answer

Shared mode for a project is fine for editing code, tests, namemapping, etc... however, I have always found shared mode to be problematic for execution. &nbsp;Usually, for execution, I have my source control download a new copy of the latest projects into a different directory and execute from there. &nbsp;That has the bonus advantage of being able to have a set of tests executing while I'm still developing without having to worry about one "stepping" on the other.

marsha_r · Answer

I'm not sure what your question is. &nbsp;Could you give us a more detailed example?

manfred_f · Answer

Ok, I give You 2.&nbsp;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!&nbsp;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_r · Answer

Your dynamic change isn't the only thing that is causing that message to appear. &nbsp;Your&nbsp;test log is changing and that will also prompt a save when you close TC. &nbsp;&nbsp;If you want to skip all the TC messages, perhaps running your test in TestExecute is a better option. &nbsp;Once you have your test behaving&nbsp;the way you like, you can run it from TE and you'll never see the main UI. &nbsp;Would that help?

manfred_f · Answer

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.&nbsp;TestExecute does not help, as it does the same storage request on Close.

Forum Discussion

using TC properties dynamically

Recent Discussions

Process "crashed" and test fails when closing the application in test

Name mapping gone

TestComplete: Connect to Azure Cosmos DB

Related Content

Changing properties dynamically using groovy script

context.expand with dynamic string not working in dynamic property expansion

Dynamically set JMS Properties from groovy code