smaloney
Occasional Contributor
Joined 3 years ago
User Profile
User Widgets
Contributions
Allow for direct comparison of expected and request response within ReadyAPI
Rather than relying on outside tools like jsoneditoronline, having the ability to compare expected response from current response would be very beneficial. A user must take the time to copy the expected and the current responses into jsoneditoronline to understand the differences when we have responses that are quite large. Add a new button to the JSONPath Match Assertion dialog to allow for direct comparison in the tool. (side by side view)JIRA integration
Hi, I set up ReadyAPI to integration to our Cloud JIRA instance so we can push issues from ReadyAPI to JIRA with the hope of creating better traceability. However, when I select the JIRA button at the top of the toolbar, JIRA opens, I select the project and issue type, then select ok. Nothing happens after that. What am I missing here? I was expecting a form to open within ReadyAPI so I can begin to enter details on the issue. I attached a quick video. Additionally, I see the attached error in the readyAPI log file. Something along the line of "Allfields is null". What is that referring to?Refactoring API definition does not properly update the version in the spec in ReadyAPI.
Our team have been going through some Swagger updates lately, and it has caused several of our old endpoints to no longer be application while adding new endpionts. So, we are refactoring our API's. We have been using the refactor option, but I'm noticing the spec version is not updated in readyapi after the new refactored API has been pulled in. In this case today, we went from 1.0.40 to 1.0.6 (yes I know that does not make sense, but that is what our dev team did). 1.0.40 was updated back in Sept 2022, while 1.0.6 was updated Jan 2023. 1.0.6 removed several old endpoints and added some new ones. The import seemed to work ok, but the spec version does not update in ReadyAPI. I've noticed this on other imports where the version progression is logical, such as going from 1.0.4 to 1.0.5...same thing. The spec number is not updated. See screenshots so it is clear which spec number I'm talking about. After the refactored API is pulled in, I'm renaming it to the right version in the left panel just so we are clear which spec was imported. This appears to be a bug...does anyone know if it has been logged yet? I can't seem to find anything on it.JSONPath Count not picking up nodes under item
Hello, I'm having a hard time getting ReadyAPI to count the nodes properly under a parent node. See screenshot. This should return a count of "3" but only returns a count of "1". I've tried adding assert by right clicking on the item as well as browsing out to the item, but I still only get a count of "1". Does anyone else know what might be going on? Is this a bug in ReadyAPI? Our whole team is experiencing this problem.
