Forum Discussion
No, I started the project on Ready API from start. And the test suites I am seeing issues are designed in Ready API 1.8.5 and I am still using 1.8.5.
I am getting this very frequently. Very hard to reproduce. But mostly by reordering the tests or cloning and moving the tests around.
- cauvery8 years agoContributor
Looks like it is reproducible easily with Assertion test step and cloning and copying to different test case.
In my case I have 2 different Assertion test steps in one test case and I am cloning and copying them to all my other test cases. Then I see this issue. Hope this helps to reproduce. The workaround for me is to exit Ready API and restart again.
I have the recording to reproduce the steps. TanyaYatskovska or nmrao Please let me know the email where I can send the recording of the steps.
Thank you,
Cauvery
- TanyaYatskovska8 years agoSmartBear Alumni (Retired)
Hi Cauvery,
Please submit the steps via our Contact Support form:
- cauvery8 years agoContributor