Forum Discussion
So stopping testing until development is done is not an option.
The automation of tests is pretty limited, manually running limited regressions & E2E since SoapUIPro doesn't support our CI
SoapUI Pro is failing to update definition requests with updated/added properties (json body) an issue I have reported.
I was more curious to find out how people break apart large projects with workspaces, git branches, story vs. regression etc.
My REST tests are all header authenticated range from simple getAllWhatever to POST requests that have dependencies pulled from across multiple other requests.
I have a plan but was curious to see what the community did.
- jasond5 years agoOccasional Contributor
"it would be good time to start for automation at least the wadl/swagger definition is fixed/concrete"
I can't wait on anything, I get a new requests to test daily, that request is concrete & complete at that moment but since it's a totally new api service there are cases where parameters, request bodies change due to ongoing dev.
- nmrao5 years agoChampion Level 3It was not interpreted correctly.
It is required to have wadl/ swagger definition to start with test simulation or automation. It is not mentioned to wait till development of the service is finished. - jasond5 years agoOccasional Contributor
I have one.
I "update definition" daily - as I have logged & said it doesnt work & only partially updates soapuipro & my requests.
Related Content
- 4 years agoUnni
Recent Discussions
- 18 hours agodipsthorat
- 22 hours agoisbiat
- 2 days agoarmygrad