Forum Discussion
Theoretically speaking, you are correct. There's no limit to how "deep" your keyword test calls can be. But, as with anything dealing with computer software, the limitations MAY be outside of the tool. If you consider call stack, you could have a memory limitation of how much memory is consumed if your keyword test calls are too deep.
- TanyaYatskovska5 years agoSmartBear Alumni (Retired)
Hi Joberry,
It's a great question. Thanks for bringing it up here.
Let me involve more community leaders in this topic so that they could share their thoughts on the testing strategy. AlexKaras, Marsha_R, Wamboo, LinoTadros, cunderw, anything to add?
- Joberry5 years agoOccasional Contributor
I have now converted all the Keyword tests to Scripts (I am happier with scripts anyway!), I have raised a support ticket to ask this question more formally.
#00427087: "Tests work until one more Keyword test is called then Test stops with Exception."
I did look at Perfmon trace during the failed execution (Memory and CPU showed benine usage), The call stack showed 4 rows, so not eaxctly huge.
- m_essaid5 years agoValued Contributor
Hi,
What is the exception ?
You could surround your script with some "try/catch" or "try/except" blocks, and then get the exception message
try your code here except Log.Message('an exception has been raised : ' + exceptionmessage); end;