tonydugay
Contributor
Joined 11 years ago
User Profile
User Widgets
Contributions
Ready API 2.2 create functional test from Swagger/OpenAPI
When I create a new functional test from the petstore.io swagger, I am very impressed with what I get out of the box - I get a lot of tests and tests which exercise POST methods provide me with a body/payload which matches the swagger definition. I was disappointed when I tried to create a test from a real in-house swagger spec - it created a test for a POST operation, but there was no body created. Does anyone have any insight as to why this might be the case? Thanks, Tony825Views0likes1Commentunsupported content-type [application/json; charset=UTF-8]
I am getting 'unsupported content-type [application/json; charset=UTF-8]' in the HTML tab of the response in SOAPUI. Is this a problem with the API under test? What would the develops need to do to stop us getting this? I wonder if this is related to my schema validation assertion failing with: Missing matching representation for request with contentType [application/json; charset=UTF-8]7.3KViews0likes3Commentswadl export less detailed than swagger import/how to add schema compliance assertion to swagger api
EDIT - I have tried a different route to convert from swagger.json to wadl format...I used APIMATIC - I find that the wadl looks much closer to what I would expect - so I will attempt to use this wadl for the schema compliance assertion in my test. I have imported a swagger definition .json file to Soapui and auto generated some tests. This all seems to work fine. I wanted to write some assertions that the developed API meets the swagger definition. If anyone has any ideas about how to do this that would be great. The initial approach I have adopted is to generate a .wadl from the project and then use that to do a compliance schema assertion. However, when I look at the generated .wadl, it doesn't seem to have anything like the detail of the .json I originally imported. For example the swagger definition tells me about the properties in the request body needed and the properties of the response object and types of the propertries in the response object. The generated .wadl doesn't have this detail. Thanks for any thoughts! Cheers, Tony1.5KViews0likes0CommentsRe: Problem with reports and statistics with LoadUI when I have a SoapUI Pro licence
Hi, Thanks for your reply. Am I right in thinking that in a sense by virtue of getting a Pro licence for SoapUI I have less functionality in terms of saving/exporting the load tests? Thanks, Tony1.8KViews0likes1CommentProblem with reports and statistics with LoadUI when I have a SoapUI Pro licence
I have a SoapUI Pro licence and I am using my tests to run load tests. I want to keep a report history of the load tests so I can watch for any trends over time. When I try and create a report in LoadUI (I have the Base Pro licence by virtue of the SoapUI licence) I am forced down the path of getting a Pro licence for LoadUI. Is there any way round this? It looks like with the open source SoapUI, you should be able to export test results for LoadUI: https://www.soapui.org/load-testing/exporting-data-and-statistics.html So I seem to have less functionality with the Pro version of SoapUI? Thanks for any help! Tony1.8KViews0likes3CommentsFinding and clicking on an object in chrome seems to take longer the first time it is found/clicked
Hello All, I was wondering if anyone else has ever seen this sort of thing/has a way of making it work faster the first time... The scenario is I find an object using Find(props, vars) and then click on it. This generally works fine in firefox and internet explorer, but seems slow in chrome - but only the frst time the object is found/clicked. I'm not talking about slight performance issues - it can be very quick in FF and IE (a matter of fractions of a second) and many seconds or minutes in Chrome. If I run my test a second time, the Chrome performance is comparable to IE and FF. It is almost as if something has been cached or compiled the second time. The issue doesn't affect all objects, just a few in my application under test - but it does mean my tests run slowly in Chrome. Any pointers would be great as I would like to be able to run the tests cross browser more often. Thanks, Tony654Views0likes1Comment