Forum Discussion
Hey AutoBear
From your description, i think it sounds like you're looking for an "Update API definitions" sort of functionality.
Have a look at here --> https://support.smartbear.com/readyapi/docs/apis/update/update.html & https://support.smartbear.com/readyapi/docs/apis/update/refactor-rest.html
Have you tried the 'Update Definition' or 'Refactor Definition' options available in the ReadyAPI! menu bar (see attached screenshot)
Do the changes to your APIs result in an updated swagger/OpenAPISpec/wadl being generated by the devs on your project? As long as you have an API definition like any of the above, you can update your existing APIs
I've used this refactor and update functionality before - although it was a while ago - and it worked well for the most part - however, I'm unsure if this is what you're looking for (I'll come back to why in a sec)
The 'Update' option handles adding new requests to a project and adding new parms to an existing request.
The 'Refactor' option handles parm, request, request payload content, operation and resource name changes.
ReadyAPI treats the API definitions as almost parents of the associated request test steps. (so like a parent/child relationship). So if you make a change to the API (i.e. changes to existing request names and existing parm name values and adding new requests, adding new parms), then the associated test step structure in the test cases are updated accordingly.
So - from your description - I think you want to Refactor your API - rather than update it - HOWEVER - I might've missed it - but I'm unsure the level of changes you're hoping to make on a project scale. If you're adding new parms - then the obviously the values associated with these parms will need to be populated again. Also - changing the existing parms, I know the parm values were nulled in the test step. Obviously ReadyAPI doesn't know what you want and can't auto-complete/auto-populate detail it's not aware of - hence why it blanks out certain values.
However - in my case where it blanked out existing values in my test step rather than just pick up what was defined in the API definition, I remember thinking that I was a bit annoyed cos I changed the name of a parm and it blanked out the values in my test step - even though I didn't think it should've. The parm name changed - it wasn't a new parm - so the value should've persisted - but it didn't. That was my only complaint but as I say - it was quite a while ago and I'm sure that issue has been resolved by now.
It was like about 3 years ago since I've (had the need) used this functionality, so any quirks probably would've been fixed by now - i'd still use the functionality again when it comes to it - it really helped, and it meant that for certain changes, I didn't have to go into every single test step in every single test case in every single test suite in my project and update the content - it was done for me!
Does this help at all?
Cheers!
Rich
Related Content
- 4 years agorajs2020