Forum Discussion
I use 4.5.1, and still see the same behaviour as you pointed the link.
However, you need not to wait for it to be fixed. There is an another way of doing using script assertion with external parameter as you wanted.
Here you go:
Define a custom property, say, SLA with the desired value in milli seconds at any level (Project, Suite or TestCase)
Let us assume, SLA is defined at a test case.
Define script assertion with the following one line of code which does the same as you expecting.
assert messageExchange.timeTaken <= (context.expand('${#TestCase#SLA}') as Long), 'SLA failed '
Hope you like it.
Hi Rao
Thanks for your response! I was thinking along the same lines as well, but was hoping that the bug would get noticed and fixed as well :)
- nmrao9 years agoChampion Level 3
Well. I believe that Smartbear team acts accordingly. And they are doing good by prioritising the new features / areas and bringing them to Open Source version most active to the customers like us.
I think when there is way, one should move on unless something is blocking.
By the way, would you like to accept as a solution, appreciate if you can.And from your posts on the forum, you seemed to be comfortable at coding, so nothing stops as groovy can do all the stuff, just explore the API. :)
Related Content
- 5 years agoComputingFroggy
- 13 years agogordillo_ramon
Recent Discussions
- 8 days agoemoya