beaston
New Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
Issues with 'Get Data' Context
Is anyone else running into frustrations in ReadyAPI 1.9.0 Soap UI NG with the 'Get Data' context menu? Here are my current issues: 1. Mousing through the menus is haphazard as it randomly will close itself out. eg. Mousing though these context menus often 3 menu layers deep results in random closing of the context menu making you have to start all over. 2. After meticulously mousing through the layers of the context menu that closes out randomly and finally getting to what you want to select, selecting it actually doesn't populate what you selected into test step properties. This doesn't seem to happen for test step 'Request Body'. I can't describe the frustration when you try to get data into a property by mousing through unnavigable context menus only to finally get to what you want to select and it doesn't actually populate in the property. Infuriating. 3. A solution that should work, IMO is using the keyboard, takes the mousework out of the context menu navigation right? WRONG. Your mouse location STILL makes the menu disappear, and you can't even hit ENTER on an option when you get to it. It doesn't select it!! This is making the product nearly unusable for what I need it for, if anyone has any ideas please I'm all ears. Mac OS Sierra, late 2016 Macbook Pro. Thanks, -Bill1.8KViews0likes3Comments'TestCase Run Steps' Should Allow for Assertions in those Steps
Currently test case run steps don't allow you to add assertions on the returns from those test steps, resulting in having to create separate extremely clunky 'Assertion' steps to assert that the data returned is what you expect when running flexible test cases. eg. Say you want to run a test case to determine the status of something and the status is returned. That status may be different depending on the test case. You should be able to assert on the returned parameters INSIDE of that testcase run step.2.8KViews1like1CommentSave application/octet-stream to filesystem
Hi, I'm using a 'Run TestCase' step in one of my tests that runs one REST Test Step that retrieves an application/octet-stream of a PDF file. What is the easiest way I can save that octet stream to my file system? Up until now I've been using a groovy script to retrieve the rawResponseData and save that to a file, but I've been running into a problem with running this TestCase in it's own Thread, where it will throw a NullPointerException when trying to use the rawResponseData. Strangely enough, it seems to work fine when the test case is called in the 'Run primary TestCase (wait for running to finish, Thread-Safe)' mode but when comes to 'Create isolated copy for each run (Thread Safe)' the rawResponseData associated to the test step is null. If there is an easier way to save this file I'm all ears because I really like running my tests in parallel and it would be nice to not have my tests grind to a halt at one step because of it not being able to run in it's own isolated copy. Thanks in advance for your help. -Bill1.7KViews0likes0Comments