Pro version 4.5 - Clone Assertions doesn't work anymore

Hello,

Can you tell us more on issue with cloning you are having?

robert
/Smartbear

I am currently running Build [internal], Build Date 2012/03/26 16:19 and I am not able to reproduce it now. It may be that my machine was low on resources, but I know there was a post during a webinar the other week that another user was having the same issue.
If the issue happens again, I'll try to gather more details.
Thanks.

Hi,

I also encountered this problem.
When the assertion step is cloned inside the original test case, it's ok, but when cloned to other test cases, it doesn't work (the assertion step appears inside the other test cases, but cannot be open!!)
I could really use a solution or a workaround for this, because I need to clone an assertion test step (which includes about 50 assertions) across 30 test cases; It would take forever to start adding them manually..
Note that I found the problem in Pro version 4.5, but I've recently upgraded to 4.5.1 and the issue is still re-creating.

Thanks,

We have had similar problems - does anyone have a fix for this?