Parse a multipart/data-form response
Hello all, In my project, I want to assert the content of the reply from my server. I send a POST request containing only a xml file, and I get a multipart/form-data containing 2 parts as a response, as expected. How do I parse those 2 parts of the response in a grovvy script ? The problem is that the "response" property of my Request only contain the first part. The 2nd seems to be lost. Thank you for your support.
Rest request attachments multipart form data for json file with parameterized json data
So I have been trying to do a scenario where i have two attachments for a rest request, one json file which i need to parameterize couple of fields from previous request. The problem with this is once you have cached the attachment you cannot modify it based on the previous test steps, So i have followed the following youtube link https://www.youtube.com/watch?v=iL-zehJmtWw Used query parameter to use a locally store file of json to request but we are getting the error from response that application/octet-stream content type is not accepted ------=_Part_01_136051460.1696260652738 Content-Disposition: form-data; name="testFile" testFile:/Path/to/file/testFile.json I have used parameter like this testFile:${projectDir}/testFile.json What should I do in this case
Basic Authentication and Cookie / Session Id
Hello, I am testing Basic Authentication on my Jenkins local server which uses username / password and then Session ID as Cookie. In RAPI, I created a Test Suite -> Test Case -> Login I created an Auth Profile "Jenkins" which has the Authorization set to Basic with the username/password. I attached this profile to the Login Test Case. If I need to preserve the session ID for the next test case, I cannot do so. The documentation suggests enabling the "Maintain the HTTP session" property, which seems to be for a Test Case with multiple Test Steps. Inherit from Parent also does not seem to take the previous session info. The only way to make it work is to reuse the Authorization Profile for every Test Case which is not the way the Application works. Please advise If I missed anything. Thanks
REST API Definition not updating properly
Hello ! A few months ago we started working on a new definition for our endpoints using stoplight, but the definition went through a lot of different variations as we learned because it was one of the first ones we worked on. In ReadyAPI, I had created test plans using the first version of the definition, and then used the definition updating functionality to update my endpoints. The testing part works properly, however when I want to use the project coverage, my responses all show as 1/1 covered with no content in the message coverage window, and when I look into the "Specification" window I can see that it's not consistent with the new definition .json file. Using "definition refactoring" also does not correct the problem. Importing the definition .json file into a fresh project will create a proper service with the right specifications and unlock the ability to use project coverage, but it will be difficult to adapt transfer all the tests manually to a new service. For example, in the old updated/refactored service I would have : "responses" : { "200" : { "description" : "OK", "content" : { "application/json" : { "example" : "" } } }, } and in the freshly create service with the same definition file I would have : "responses" : { "200" : { "description" : "OK", "content" : { "application/json" : { "schema" : { "$ref" : "#/components/schemas/PlaceholderAPIBR" } } } }, } Is there a way to update the old service API with the new definition and force it to use the new response format ? The definition file also changed location and name when we started sourcing the project using Git, but I can see that the "original definition path" in the specification window and the "definition" service property are still showing the old file path. I'd rather not have to change all the tests, considering the main ReadyAPI project consume multiple services and not all of them have the issue.Fetch Access token using OAutho0.2 - Implicit Grant
Hi, I have scenario to test ready api but that works when AccessToken is entered. So till now i have managed by entering the access token in below UI by fetching it from Access Token from UI I tried Implicit Grant but here when i click on get Access Token an UI will appear . I have written automation code in Autho Mangr-> automation code to click on Autho Selector type . But i can see it does not work at all. Here, i want to know how can i get the access token using implicit grant or is there anyother way where i can launch chrome browser and select ADFS-> Click login and ->Copy the Access token and save it into and variable and pass it into above Access Token textbox. Note - I decided to go with Implicit Grant because client is not okay to share client-IDExpecting claim 'qsh' to have value error message
Hello, I am trying to call endpoint https://prod-api.zephyr4jiracloud.com/connect/public/rest/api/1.0/execution but I am still getting 401 with message Expecting claim 'qsh' to have value 'bd5...' but instead it has the value 'b21...' I have followed documentation from https://support.smartbear.com/zephyr-squad-cloud/docs/api/jwt-token.html where I first generate API keys in Zephyr in Jira, generated keys used for JWT token with attached code inside documentation and then calling aforementioned API endpoint with curl command, but still getting same think. Can you please anyone help me/explain me, what might cause this issue? Thank you in advance,
