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,
If you are using Git you may be interested in the Git Console that was recently added as a ReadyAPI update. This integration will let you make .git calls directly from the console after connecting to your remote repository. For more information on the Git Console please visit the link below.
https://support.smartbear.com/readyapi/docs/integrations/git/console.html?sbsearch=Git
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.
Hello cadesnoy65
Yep. That is strange problem. Not one I can reproduce. I can only suggest a work around and see if that helps...
Instead of having assertions on the api invoke test step, maybe have the assertions in a groovy test step. Is the issue only related to assertions in one api invoke test step for one test case or assertions in any api test step in all test cases?
I prefer assertions in a groovy test step so they are not buried deep in the api invoke test step that I have to crack open each assertion to see what it is evaluating. I like to see all the assertions in code at one time.
This issue does not seem to be wide spread (at least others are not reporting it) so that leads me to believe something is specific to your situation. Is it a big project or one that has been modified a lot by different people with different versions of ReadyAPI? Maybe save it back to a monolithic xml project and then back to a composite project to see if it heals. I don't have an answer.
Regards,
Todd
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.
