Contributions
Re: Assertions not saved in Ready API 3.9.0
Not really, we have a big project. I can't change everything to use assertions in groovy instead of the assertions features. I can't also switch from composite project to normal project. But I appreciated the responses.3 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.3KViews0likes1CommentRe: Assertions not saved in Ready API 3.9.0
I updated to version 3.10.1 and I still have the same problem. It's very difficult to work with that. I'm thinking of using another software. It happens when: I rename an assertion I change the contents of an assertion I clone an assertion Example of the problem. There is no message in the log. Except that everything is saved. But it's not. Not sure, but I think it happens after a test run. if we open Ready API and change assertions, it will work. But after we run the tests, the save is not working good.(but not every time) I have to investigate.3 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.4KViews0likes4CommentsRe: Assertions not saved in Ready API 3.9.0
Thank you. I did what you said and there is noting in the log except "Saving Test Case..." but nothing was saved. I will continue to look at the log, Which version of READY API do you use ?3 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.6KViews0likes8CommentsAssertions not saved in Ready API 3.9.0
Since I have Ready API 3.9.0, I have problems when I save my project after I modified an assertion. When I close Ready API and reopen it, my changes are lost. Has anyone ever had this kind of behavior. It's not all the time, and I can't find a pattern. I'm using composite project. After the save if I look in the XML file of the Test, the changes are not there.1.8KViews0likes10Comments