Hello,
I do have exactly the same problem.
It seems to me like the Runner object holds all references to variables and breakpoints. And when calling Runner.Stop this object gets disposed and a new Runner object is created which starts with the next test item in queue, but has no idea of any variables or breakpoints.
I did not yet check this with Project variables, just with a global script unit which holds the information I need throughout the tests.
Kind of makes me feel like my test architecture is not correct, because like this the Runner.Stop method is completely unusable.
Anyone else having any experience with this?
Regards,
Christian.
EDIT:
Project Variables do in fact keep their value after a call of Runner.Stop (true)
I do use this runner.stop to end the current test item and proceed with the next test in line.
The GeneralOnLogError script code is in "MySubs" unit.
Running a Project starts TestItems one after the other, if one test item fails, the GeneralOnLogError event is triggered. In this logEvent, I call the runner.stop.
My understanding is "MySubs" is a child of MyProject and MyTestItem. So with this in mind, my global variables are defined in the MyProject so they do not die with MyTestItem ending.
