lgermain315
Occasional Contributor
Joined 10 years ago
User Profile
User Widgets
Contributions
Re: Accessing data content using "RawRequest" variable returns null even though a request object present
Hi, Thanks for your feedback, however these seem to be work arounds for the problem. The original functionality that was in place seems to have been broken. Here's another video that shows the desired behavior: https://www.screencast.com/t/CKKqCa3vXQu UPDATE: I found that my request object had 1 trailing comma which caused the json to be invalid. Version 2.2 ignored this comma and version 2.4 does not and writes an error to the log. Once that comma was removed, the 'RawRequest' dialog showed up and worked as expected. However, there are still issues using "Select Content" drop-down within the asserion dialog. I will not use this anymore. Instead use the right-click context menu "Get Data" and use that dialog to achieve the desired results.1.7KViews0likes1CommentAccessing data content using "RawRequest" variable returns null even though a request object present
Using version 2.4.0, I have test that fail now because the "RawRequest" data is null. In the past when you, use "Get Data" you could access the request body and use that variable for an asserions. It seems that this "RawRequest" variable is null. Could there be a setting that I need to enable to access the request body? I have test history disabled and max results set to 1. Video Showing the Issue trying to access "RawRequest" https://www.screencast.com/t/RaNIsVjb thanks, Luke1.8KViews0likes5CommentsRe: <BUG?> Check for existence JSON Node no longer works as expected in 2.3.0
Hi Steven, I've updated to the latest "ReadyAPI 2.3.0-m-SNAPSHOT" (https://support.smartbear.com/downloads/readyapi/maintenance) however, this 'existence' assertion still fails for null values. Fyi, I could not find the original bug submission: Case: 00286704. SoapUI Version 2.3 will fail 'existence' assertions if the property has a value of NULL. This is a new change and effects the existence assertion definition. Thanks, Luke2.1KViews0likes0CommentsRe: Soapui 5.3.0 - Security Test - How to Send Fuzzing Scan Input into a Request Body?
Thanks for your input and scripting solution. I kind of figured it would not work since XPath is for XML and JSONPath is for JSON, but thought there might be a work around using the security tool. I will go ahead with the script you have provided as an example. Thanks again, Luke2.7KViews0likes1CommentSoapui 5.3.0 - Security Test - How to Send Fuzzing Scan Input into a Request Body?
Hi, I have a POST request with a JSON body and would like to understand how I can injection invalid inputs such as cross-site scripting, sql injection, fuzzing values into the Request body using SoapUI 5.3.0 open source tool. Here is the raw request example below: POST http://ngetest.callminerhq.callminer.net:8080/api/v2/users HTTP/1.1 Accept-Encoding: gzip,deflate Content-Type: application/json Content-Length: 148 Host: ngetest.callminerhq.callminer.net:8080 Connection: Keep-Alive User-Agent: Apache-HttpClient/4.1.1 (java 1.5) { "Email": "sample@test.com", "FirstName": "sample", "LastName": "test", "IsEnabled": 1, "Password": "test123", "ChangePassword": true } See the 'Email' field above, I would like to run a fuzz scan (and other security tests) on this input property. Here's what I have so far but could not quite understand how to get this working. Currently, the 'Email' field does not change value and simply runs with the body above (result = duplicate email field is prohibited thus we receive a 400). Screenshot: https://www.screencast.com/t/jgOrX51SYkKF Basically, it seems that my XPath string is not correct and I'm not entirely sure how to interface with a request object. Maybe someone could help me break down this XPath string. Any help would be appreciated. Thanks, LukeSolved2.9KViews0likes3CommentsBug: Cannot save a regex statement for JSONPath RegEx Match Assertion
Hi, I've noticed an issue where I cannot update or save a JSONPath RegEx Match Assertion. Video: https://www.screencast.com/t/TbaFrirmOFUf Test Steps: 1. Open Ready! API version 1.9.0 2. Click SoapUI NG Pro tab 3. Go to an existing test step. 4. Expand the assertions tab 5. Click "+" to add a new assertion. 6. Find the JSONPath RegEx Match Assertion. 7. Locate an item with JSON, add a regular expression to the text box. Click Save. 8. Reopen the assertion you just created. Here you will notice the regular expression is missing and did not save properly. Expected behavior: The regular expression is preserved during a Save.Solved3.1KViews0likes4CommentsRe: Run Test Case as test step failure
I just submitted the same bug (duplicate) as listed here under the following title: [Bug] Run TestCase (Test Step item) can only be run once then fails repeatedly. I've also included a video as well. Video: http://screencast.com/t/il0cVbG787yJ5.5KViews0likes10CommentsRe: Run Test Case as test step failure
Title: [Bug] Run TestCase (Test Step item) can only be run once then fails repeated. You must close/restart program to run again. Suimmary: The test step item, "Run TestCase" can now only be run once then fails until you close/restart Ready API. After running the first time, the REST requests within the Test Case are removed and the test case instantly fails. See the video link below. Video: http://screencast.com/t/il0cVbG787yJ Any help would be greatly appreciated. Thanks.5.5KViews0likes0Comments