Contributions
refactoring of WSDL
Hello, we have to refactor some projects because of changed WSDL definitions. Using the refactoring feature of SoapUI some questions popped up. We got the screen with the graphical presentation of the changes between the original WSDL and the new one. A lot of links point to definitions in the new file which are marked as ‘not in schema. Disconnecting the links enables us to reconnect the previous xpaths to the new ones – partly. The following problem occurs: if a field moves to a lower level – which means in the new WSDL definition a level has been inserted – it cannot be connected to the new structure. In the screenshot attached you’ll find a field aeaBorder cannot be connected to the aeaBorder in the new WSDL because the level AreaLayout has been inserted. Is there any solution how to link the two fields? Request definitions and Response definitions created in some test cases get lost after finishing the refactoring process. Because we have a lot of test cases (about 400) we shall to find a solution how to migrate also the test case request definitions to the new schema. Please let me know what’s possible to migrate to the new schema without loosing request and response definitions and how to migrate properly when levels have been inserted in the new schema. Thanks in advance Greetings Andi Kollenbach12 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.7KViews0likes4Comments[Resolved] Webpage not readable
Hello webmaster, with the new homepage on http://www.soapui.org the menu on the left side is not readable for me. The entry buttons are coloured grey, the characters are black. Is it possible to change? Greetings Andi12 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.6KViews0likes4CommentsRe: avoiding compression of responses
Response from a file has been read as shown in your example at Mock Operations and Responses at the bottom of the page. The repoonse in the file is uncompressed pure XML. Greetings Andi12 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.1KViews0likes0CommentsSoapUI sends same response twice
Hello, I created the following test case: - Mock response - data source from an execl file: read filename into property fileName - mock response with script - data loop to mock response with script The script used to manipulate the content of the response is this: def project = mockResponse.mockOperation.mockService.project def testSuite = project.getTestSuiteByName("Bulk tests") def testCase = testSuite.getTestCaseByName("GetVrListFromMultipleFiles") def testStep = testCase.getTestStepByName("GetDataFileNames") def projectPath = project.getPropertyValue("projectPath") def testDataPath = project.getPropertyValue("testDataPath") def fileName = testStep.getPropertyValue("fileName") log.info "reading file " + fileName context.content = new File(projectPath + testDataPath + "\\" + fileName).text log.info context.content where the properties projectPath and testDataPath are properties set manually. The fileName property is read also correctly and the file can be found. The log.info writes the content of the files correctly to the log file with the content expected. The test case runs 5 iterations. The test step used for the manipulated mock reponse has been inspired by the example of the chapter Mock operations and responses (http://www.soapui.org/Service-Mocking/s ... viour.html) Nevertheless, the program under test - which sends the requests - records the same response content in each iteration The program under test receives the same response in each iteration - which is definitely not intended.12 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.9KViews0likes3Commentsavoiding compression of responses
Hello, in a test case a mock response test step reads the response from a file and sends it back to the requester. Unfortunately the response will be compressed using GZIP. How can I avoid the compression of the SoapUI response? Greetings Andi12 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.8KViews0likes5Comments