Forum Discussion
Is this defect SOAP-3629 has been fixed?
We are having the same issue (Ready API overwrites other user's work in Composite Project.). The testing team at AAA is using this version - API Ver. 1.7.0.
Please let me us know. The email is - sjohn@aaamichigan.com
Yes, this is still a major issue for us. I retested it again today, and it is still happening. We have ReadyAPI 1.6 here, with composite project format 1.2. MarcusJ (Smartbear Support) confirmed this issue exists with composite project version 1.3 also, on 17th March.
Tanya Gorbunova (Smartbear Community Manager) discussed with Support yesterday.
Today (6th May) , Marcus sent email stating "A new internal defect was opened for your scenario, after this was discussed with a Ready API developer and product owner of API-4889. This defect is still open, will ask the product owner to prioritize the defect.".
We have no "workable" solution or workaround for this, so all testers must be ultra careful, and check with all other testers before any "save". It is a matter of time till we get another "overwrite" , where test case updates are lost and test step updates are lost.
I will forward this post to your email addr. Regards, PhilK.
- frame28 years agoNew Contributor
we do use version control but this is still a problem - a lot of the .xml-Testcase files are updated even if we did not touch them - the diff looks like some internal id's there have changed. Sometimes you just open and close readyAPI and subversion shows several modified files and wants to commit them ...
So even when using version control we have to be extra careful to not commit testcases which have been "really" modified by others - there are so many conflicts that this happens easily ...
- PhilK8 years agoNew Contributor
21st July 2016 - SmartBear closed the case #00087837 stating that it has been resolved , but Defect API-4889 is NOT mentioned in the Ready API 1.8 Release Notes or in the SoapUI NG Pro 1.8 Release Notes.
I requested this bug be RE-OPENED , until the Release Notes include API-4889 defect. Phil Kronk.
- AlexeyK8 years agoSmartBear Alumni (Retired)
Hi Phil,
That bug has been fixed in 1.8, we updated the release notes for you.
Sorry for inconvenience.
Typically, developers close more issues than you can find in the release notes.
So, in future, you can believe the email messages from the Support Team - they are correct :-).
Best regards,
Alexey
Related Content
- 7 years agoJSoul