I was hoping that
ExitTest would send a status of "Not Complete" to ALM.
I see in the F1 documentation:
Exits the entire UFT test or ALM business process test, regardless of the run-time iteration settings. The pass or fail status of the test remains as it was in the step prior to the ExitTest statement.
I need a way to tell ALM that the scirpt did not run to the end.
Does anyone know of a way to set ALM status to "Not Complete?"
Pressing stop on the runner will result in a not complete. Maybe you can invoke that by getting a hold of the current run with OTA instead of using the exit test. I have doubts whether that is possible while in the UFT run though.
Sometimes UFT throws a fail. I don't know what the fail is for. It is not during a test point. The navigation is fine. I do not have an example handy but there are fails that I am not concerned about. I do not want these to be considered as an applicaiton undertest fail.
If I am running a keyword driven test and the user stops the script remotely by placing a value in a flat file, I want UFT to stop and consider this to be Not Complete.
In other words there are times and places where I have a valid reason to over ride UFTs decision.
I don't believe you can do this as part of your test run - the run will have its own 'final' status that it will set, and it will do this at completion.
Something I noticed when I was writing a tool to create run data in ALM11.5 was that after creating the RUN I had to specifically set the Instance state also, which felt like a double post.. but it didn't work without it.
I can hunt for the code if you like.
By double post do you mean the .Post method?
Do you have a way of getting the Status to stick in ALM from inside of the UFT run or do you have do it through the OTA?
if the double Post lets me set the final Status I would like to see the code.
These are all methods done outside of the run using OTA.
One thing you may be able to do is to turn reporting off with the filter, do custom reporting, then at the end turn built in reporting back on and set the status before the uft run finishes. But even then you'd still be left with choosing a pass or fail don't think not complete could be an option.
You'd likely have to go to a full custom reporting solution to achieve this. And the posting of results back to QC would likely have to be async after the fact with OTA if you want to use the QC test runner. Would probably be best to just write your own driver/runner.