Hi,
Nope. And I am fully in line with what Marsha has written.
Any more information as for why do you need scripting access to these properties?
However, regardless of the answer 🙂 I see only two options:
a) Project file parsing and modification before test start. This is generally not recommended and you may do this on your own risk;
b) Implement retry functionality in code. But, depending on your requirements, this might appear to be not a trivial task.
Something like that:
-- Create a loop;
-- Call actual test code from within this loop;
-- Test code must set some flag (e.g. via the project variable) that indicates whether or not test should be rerun. Additionally, this flag may be manipulated by event handling code (e.g. OnLogError);
-- Loop or exit from the loop depending on the flag's state.
