MFagerlind
StaffJoined 12 years ago
User Profile
Staff
User Widgets
Contributions
Re: ReadyAPI 2.0?
Hi jhettic, Thanks for reporting this! We've isolated the problem with some test step changes not getting saved properly, and a fix has been added to the latest maintenance build, which can be downloaded from this page: https://support.smartbear.com/downloads/readyapi/nightly-builds/ Even though the URL includes the somewhat scary word "nightly builds", these builds are actually pretty stable, not cutting edge. The maintenance builds are very similar to the latest release builds but with some bug fixes. If you're unable to use the maintenance build (maybe due to a company policy etc) but still want to try 2.0 before the next release, where this fix will obviously be included, a simpler workaround than the one you tried is to rename the test step you modified before saving. Most changes generally will make Ready! API realise that it needs to save the project. Sorry for the inconvenience! Kind regards, Manne, Ready! API developer4.4KViews2likes1CommentRe: Generic assertion.
Hi Mishka, Just to be clear, the script below won't work like an assertion, in that it won't add an assertion result in the GUI, etc, but it will allow you to fail a test case and will log the reason in the script log. This may not be enough for you, and it's clearly not a substitute for the full feature - thanks again for the suggestion! def testStep = testStepResult.testStep def responseContent = testStep.testRequest.assertableContent if (responseContent.length() < 100000) { def failureMessage = "Response content to short - test step: $testStep.name" log.error(failureMessage) testRunner.fail(failureMessage) } Regards, Manne11KViews0likes0CommentsRe: I can't work out how to run secure with proper JSON parameters
Hello! Sorry for the late reply, I thought my fellow developer had already replied to this. Injecting values into JSON has been pretty excruciating in Ready! API Secure, but it's just become easier. In version 1.9 you will be able to extract the JSONPath for different values in a JSON Post automatically, just like we've extracted XPath in earlier versions. Try it out! Kind regards, Manne, Ready! API Developer1.6KViews2likes2CommentsRe: Updated to Sierra and SOAPUI 5.2.1 does not load
Hi, We can't reproduce this in the development team - SoapUI starts fine for us on a Sierra machine. We will try on another one later today. Meanwhile, we'd be very grateful if you could help us troubleshoot this! If you send me a private message I'll tell you how. By the way, jre.bundle is the Java runtime, so that workaround shouldn't work unless you have another Java runtime installed. Kind regards, Manne, Ready! API developer1.5KViews0likes5CommentsRe: run vba macro from groovy
Hello, Sorry that you're disappointed, but asking a question in the forums is not the best way to get support. If you have a SoapUI Pro license, you're entitled to support, so you should open a ticket with Customer care. They will help you, and if they can't they'll reach out to us, the developers. Kind regards, Manne, Ready! API developer3.1KViews0likes3CommentsRe: Edit and Submit RAW request without using "Request" tab
Hi Greg, I looked into this and initially thought you could achieve this with an Event handler of type RequestFilter.filterRequest, which is a good Swiss army knife for modifying requests in various way, but it turns out that direct manipulation of the query string is a bit too low level. It'd be great to have an event handler that fires just before you're sending the request, and I will make a feature request about just that. Meanwhile, I hope that the workaround you came up with is OK. Regards, Manne, Ready! API developer5.5KViews1like1Comment