Contributions
How to update test payload from REST resource's request definition?
Hi all, When I update aresource's path, or add query/matrix parameters to a resource, these changesget "pushed" down into the test steps that rely on (i.e. are associated with) that resource. I'm wondering if the same functionality is available for payloads (request bodies) and request headers? For example, given a REST project consisting ofa resource that supports a PUT request with payload, and a test case for that resource request, is there a way to update the resource request's payload and/or headers, and have that (change) reflected in the test case's test step? Put differently: How can I push updates from a REST resource definition to associated test steps (when they concern the request body or request headers)? Brgrds, Christian1.1KViews0likes0CommentsTests with different payloads for same REST resource (endpoint)?
Hi all, Let's say I have a REST service that allows you to search for rail journeys - and that once you have selected them, you can book them. The endpoint is example.com/service/v1/book, and to create the booking, you use a POST. Because in reality, when you get to the booking state, the request would require a lot of data, the details of the booking are send as JSON. For simplicity's sake, let's assume the body just takes the journey legs at the moment: { "journey" : { "type" : "return", "outgoing" : { "from" : "LON", "to" : "NCL" }, "return" : { "from" : "NCL", "to" : "LON" } } } Now, for a one-way ticket, that bit would obviously look slightly different, yet the resource (or HTTP method) wouldn't change - it would still be POST example.com/service/v1/book: { "journey" : { "type" : "single", "outgoing" : { "from" : "LON", "to" : "NCL" } } } The service would have to deal with it slightly differently, though. So, we'd want to test both. How would you structure that in SoapUI? I thought you'd create the resource (with the POST method), then create two different test cases, "one-way" and "return". What I'm not sure of is how I'd then be able to pass the different payloads in? And where they'd be defined...? Any ideas? Kind regards, Christian P.S.: I previously posted this on StackExchange: http://sqa.stackexchange.com/q/16368/68461.6KViews0likes1CommentIs there a Jenkins plugin that visualises SoapUI test result
Is there a Jenkins plugin that visualises SoapUI test results by giving you a graphical report? I'm basically looking for something like this, but for SoapUI: SoapUI displays results in a really nice way in it's GUI. Any chance of getting something similar for/when it runs on Jenkins? Regards, Christian P.S.: This is a cross post from http://sqa.stackexchange.com/q/9174/68468.2KViews0likes6Comments[5.0.0] Boundaries/Restrictions not picked up from schema
Hi all, The bug [4.6.4] Boundary tests not working (skipped) is still persistent in version 5.0.0. The offending code line is now here: com.eviware.soapui.security.boundary.BoundaryRestrictionUtill:40 if( "xsd:restriction".equals( mynode.getParent().getNodeName() ) ) Surely, if other open source libraries (like schema validators) can figure out what the correct standard namespace is, so can SoapUI - or ignore the namespace all together, e.g. by just looking for if( ":restriction".equals( mynode.getParent().getNodeName() ) ) As it stands, that bug stops boundary scans from working for all schemas that don't use "xsd" (but instead e.g. "xs") as their standard namespace. Will this be fixed anytime soon? Kind regards, Christian10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1KViews0likes0CommentsRe: [4.6.4] REST: How are the PLAIN parameters used?
Looks like the following does the job, albeit not in a pretty way: && "PLAIN" == e.value.getStyle().toString()) Has anyone an idea how to do this comparing to the ENUM or how to get the values using SoapUI's Property Expansion?1.9KViews0likes0CommentsRe: JSON parameters and POST request parameter handling
@EricB: that's super useful, thank you for sharing! Is there a way to check if a parameter is of type PLAIN at all? The ENUM to assert against is probably this one: http://www.soapui.org/apidocs/com/eviwa ... Style.html Unfortunately I don't know how to access the "Style" (e.g. "PLAIN") of a parameter in Groovy... Also, is there a way to access PLAIN parameters using Property Expansion? Brgrds, Christian11 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.6KViews0likes0Comments