LennSar
Contributor
Joined 3 years ago
User Profile
User Widgets
Contributions
Re: Swagger Compliance Assertion: Invalid content type [image/bmp]
Hi KarelHusa, thanks for the suggestions. I forgot to say it because it became so self-evident for me to have a proper OpenApi.yaml. image/bmp is the defined content-type in the swagger UI so the compliance assertion actually should get it right. Maybe you see something in our definition that I don't see: LennSar wrote: Hi there, I wonder why I get the error mentioned in the topic. The image is properly transfered and displayed. Also I think image/bmp as a content type should be allowed. Any suggestion what could go wrong here? Thanks in advance! /screenshot.bmp: get: servers: - url: http://{Hostname} description: http direct variables: Hostname: default: 169.254.2.0 description: Hostname of the device - url: https://{Hostname} description: https direct variables: Hostname: default: 169.254.2.0 description: Hostname of the device - url: http://{Hostname}/{ID} description: http forward variables: Hostname: default: 169.254.2.0 description: Hostname of the device ID: default: "1" description: System ID of the device enum: - "1" - "2" - "3" - "4" - url: https://{Hostname}/{ID} description: https forward variables: Hostname: default: 169.254.2.0 description: Hostname of the device ID: default: "1" description: System ID of the device enum: - "1" - "2" - "3" - "4" summary: Get a screenshot operationId: GET_screenshot.bmp responses: "200": description: Screenshot in BMP format content: image/bmp: schema: type: string format: binary "405": description: Method not allowed. Rights missing?1.2KViews0likes2CommentsSwagger Compliance Assertion: Invalid content type [image/bmp]
Hi there, I wonder why I get the error mentioned in the topic. The image is properly transfered and displayed. Also I think image/bmp as a content type should be allowed. Any suggestion what could go wrong here? Thanks in advance!Solved1.4KViews0likes6CommentsRe: Fail Test Case only if it ENDS with failed Test Steps
I still don't quite understand how that would differ from any other assertion. A script assertion would decide between 'wrong' and 'right'. If "Fail Test Case if it has failed Test Steps" is enabled a single 'wrong' detection would cause the test case to fail. A workaround would be to do nothing in the wrong case but that would result in a passing test case in case something really is wrong. I could only imagine a script that implements the loop for sendin the rest request several times and do a final decission on the whole thing but that would be quite an effort compared to just adding a smart assertion ...775Views0likes0CommentsRe: Fail Test Case only if it ENDS with failed Test Steps
Thanks for the suggestion. I don't quite understand how that would solve the issue. The script assertion as the smart assertion would fail the first couple of attempts and than would succeed. In a bad case both approaches would fail identically and without the enabled "Fail Test Case if it has failed Test Steps" option the test case would end up as a 'pass'. Am I missing something?813Views0likes1CommentGet Rest Call Coverage based on OpenApi yaml file
Hi there, I saw that ReadyApi somehow supports a metric for the test coverage but I can't see the buttons suggested by the tutorials in the documentation. And I wonder whether it actually is what I'm looking for. I'd like to have a list of all Rest Request in the OpenApi yaml with the information of how many times it is used in the according project. Does something like this exist in ReadyApi? Thanks!389Views0likes0CommentsFail Test Case only if it ENDS with failed Test Steps
Hi there, I have a test case that runs a rest request up to 10 times. The first few iterations pretty sure will not meet the requirements of the smart assertion but at the 10th iteration it must do! My problem now is that by default ReadyApi consideres every TestCase a fail if one test step failed. Therefore I disabled the checkbox "Fail Test Case if it has failed Test Steps" in the test case option. Unfortunately the behaviour now is that the Test Case always passes even though my Test Steps fails at the 10th iteration after which it simply proceeds with the rest of the test case. What I'd like to have is the option that the test case results in a pass only when all Test Steps at the end of the Test Case are pass but each Test Step is allowed to fail inbetween. I'm pretty sure there is a solution to this and tha the answer is somewhere in the forum. I just couldn't find it. Some additional info: I do the rerunning of the paticular test step either with a groovy script or a conditional goto. In Case of the groovy script I could manually fail the test case. In case of the Conditional Goto however this is not possible. Any suggestion would be highly appreciated. Thanks in advance! Lenn938Views0likes4CommentsGroovy Serial Communication
Hi there, I'm testing the Rest API of a device which also needs some configuration via serial communication (RS232). Does anybody know about a groovy library to do that? If not I would probably write a Python script and execute that from groovy. That should be possible right? Any suggestion is highly appreciated!403Views0likes0CommentsRe: finish test case as is. Not canceled, not failed!
at the end it simply doesn't matter whether it's a rest call or a delay or a groovy script that I jump to. It's all the same approach which isn't my prefered way to begin with. What I was hoping for was something like testRunner.finishSuccessfully or something like that but unfortunately there is no such thing....1.2KViews0likes0Comments