Forum Discussion

Manfred_F's avatar
Manfred_F
Regular Contributor
9 years ago

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 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.

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

    • Manfred_F's avatar
      Manfred_F
      Regular 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_R's avatar
        Marsha_R
        Moderator

        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?