Assertion test step becomes unusable for a cloned test case

Not aware of any thing called assertion test step.

Do you mean that, you have a test step and it contains some assertions. This is all your case is? If not, would you please care to write the case in details or with a screen shot for better understanding of the case?

Hiya

right click and add a test step - last item in the list Assertion TestStep

screen shots attached of test step in question and the cloned one (note cloned the entire test case),



I was cloning the 1st test case in the list, after doing so the test runner cannot be used at either the top level or individual level for that test case, individual level for the other test cases is ok
note the source is DELETED ELEMENT for the grouped assertion in the cloned copy, clearly losing some referential link there during the clone process
as an additional note the 3 parties response assertion test step cannot even be accessed

as I mentioned the only solution found so far for this is to revert back to a previous project xml file (I'm not going to start fudging about in the xml file )

Thanks for reporting this. We will try to reproduce it and (if we're succeed) add it to the backlog for prioritization.

Cheers!

Manne

PS: If you have any error logs with the NullPointerException, we'd love to have a look at them.

No worries

if you follow the link in the first post there's a copy and paste of the error produced in the error log when opening the test suite editor

regards
Mike