Assertions 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 behav...
Forum Discussion
Hello @cadesnoy65
That is a painful issue... I might have encountered that a very long time ago, but don't have a direct solution for you since it has not happened to me lately.
The first thing I would do is see if ReadyAPI is letting you know there is an issue by looking at the ReadyAPI Log (lower left corner of ReadyAPI | Show Logs). Click on the "ReadyAPI Log" tab and right click anywhere in the log text area and select the "Clear all logs" menu item. Once you have a clear viewing area it will make it easier to see what ReadyAPI does when it saves your project. Now that the area is clear, make your assertion change and watch the ReadyAPI Log viewing area when you save your project. Scroll through the viewing area after you save and see if there are any warning or error messages in the log that you might be able to address.
Since you say this problem does not happen all the time, you may need to view the log each time you save to see if anything strange is noted in the log. Without log information, everyone answering your question will just be guessing on what the solution might be.
Regards,
Todd
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 ?
Hello cadesnoy65
Currently I am on the latest version (i think) 3.10.1. I always update to the latest version when it comes out since I have not been bit by new versions for a while.
I see the word "Git" in your file path to that testcase xml file so that leads me to believe you might be using the Git feature of ReadyAPI maybe? I work on files that are under the control of Git but I don't use the Git feature built into ReadyAPI. Opening and Saving files are a pretty standard feature of ReadyAPI, so if there were more issues with that version of ReadyAPI, I would think there would have been more outcry with people in your same predicament. My only thought for your solution might have something to do with Git if that is part of your workflow. That path to your filename looks really long too. Windows usually can deal with that almost 200 character fully qualified file name, but there could be something fishy with that too.
Unfortunately, that log looks like ReadyAPI is working with that file just fine, so my suggestions would just be speculation. It might be a little continued trial and error research for you into what the root cause is. Regardless, that is not a common complaint for ReadyAPI use.
Regards,
Todd
Thank you for your answer,
I use Git but it's not Git feature of ReadyAPI.
I will try to upgrade to version 3.10.1. Maybe it will help
