Thank you for your investigation, it really helped a lot.

Is it possible to share your UFT test so we can continue investigation? you can attach a zip file to this issue. We tried to run a simple UFT test, it was not marked as dirty, I can't think of any case that may cause the test become dirty.

I looked into the github change you posted, closing UFT regardless if it has a dirty test is an option but it is risky that we would like to run a full test before add this fix to our next release.

i will keep monitoring this thread, hopefully the problem can be solved soon.

OKay. So I just did a run again and used the git diff to tell me the differences.

Our scripts do modify the design-time datatable as well not just the Run-time aka After a script is finished, the content of the run-time datatable is transferred back to the Default.xls file of the Test(which is the Design time table).

Our developers are using this as an easy way of persistence . In this way it is very easy to do run from steps and debug from steps.

I noticed that the QtpTestCleanup is used in other places as well, so your concerns are valid.

As an alternative we would propose then the explicit edition of Test.Close after a test was executed.

In  this way all the other use cases could remain intacted, and use cases like ours(I am sure we are not the only one using UFT in such unorthodox ways) could still go on.

Glad to hear that you found root cause.

We had a discussion about this issue moment ago, we will change the error message from "unable to launch UFT" to "Unable to close UFT due to unsaved test", whether save the test or not is left for user to decide. You should be able to see the change in next release.

Thank you for your time and effort.

xiwen zhao I understand this issue is resolved?

Hi Daniel,

Due to release plan change this defect was moved to future release. It appears to have low priority because changing error message does not really solve the issue, it only gives a better hint for users.