Solved
Forum Discussion
TanyaYatskovska
SmartBear Alumni (Retired)
Hi TwoFang,
From my understanding, the code that used to work fine in v. 1.6 should work in the new version without any issues. I recommend that you contact our Customer Care Team so that they could investigate this.
Please share the solution with us once you find it.
Thanks in advance.
TwoFang
8 years agoContributor
After creating a support ticket it's have been confirmed that this is indeed a bug and it's been added to the backlog