blade
Occasional Contributor
Joined 10 years ago
User Profile
User Widgets
Contributions
Re: [Ready API 1.2] Double slash (//) in path
Hi, Has there been any update from smartbear on this issue? I am currently getting this error in Ready API 1.5.0. Will this be addressed in the next release? It has a downstream impact that when I run a Test Case, upon reaching the last step it takes approx 15-20 seconds to complete.9KViews0likes6CommentsRe: SoapUI NG Pro 1.4.0 - JSON Response view removing decimal points
If I use another tool like postman, the Raw Response is always displaying 0.0 for me. This is the value that I assert against. In the JSON View (Pretty Print as they call it) in postman it displays as 0. This currently matches with Ready API 1.5.0 behaviour. We could wait for a reply from smartbear and see if it would be possible to have a config setting in preferences to assert against the Raw Response or the JSON View.5.3KViews0likes0CommentsRe: SoapUI NG Pro 1.4.0 - JSON Response view removing decimal points
Hi austino, That fact that it is asserting 20 is the error. In the actual response you receive, viewable in the 'Raw' tab. the actual value will probably be 20.0, while in the JSON tab its been displayed as 20. When the fix was made I also had to go through the pain of updating over 1000+ test cases and each test had multiple assertions for decimal values. The whole purpose of this fix is to make sure that what is returned from the API is the actual value been asserted (tested). The problem lies with the older Ready API build that was used, in which when the original assertion was created it was taking the incorrect 20 value instead of 20.0 which is the value been returned in the API response. I welcome any input/opinion from Smartbear on this issue. Regards,5.3KViews0likes2CommentsRe: Unexpected error when running test case that has groovy test step in 1.5.0
Hi Tanya, Support supplied me with the following steps that resolved my problem. Please try to re-enable the Test Run History: 1. Remove the "-Dtest.history.disabled=true" option to the <R!API installation folder>\bin\ReadyAPI-1.5.0.vmoptions file. 2. Update the Test Run History database (http://screencast.com/t/x0GRPJCp). Regards,4.8KViews2likes1CommentRe: Unexpected error when running test case that has groovy test step in 1.5.0
Hi Tanya, I have installed the latest maintenance build of 1.5.0 and the issue is still occuring, but it is not localized to tests with just a groovy test step. It is happening with all of my tests. Upon running a test it gets to the end, but all test steps remain greyed out and test does not complete. In the Ready API log the following error is displayed: Wed Nov 25 07:16:41 GMT 2015:ERROR:Error notifying listener after run java.lang.IllegalStateException: Test history is disabled When I re-enable the test history and run the test again I get the following error message: Wed Nov 25 07:24:45 GMT 2015:WARN:Not storing test run data for TestCase '05. Terminal Info' since there is no repository. Wed Nov 25 07:24:45 GMT 2015:WARN:Not storing test step run data (latest runs) for TestCase '05. Terminal Info' since there is no database repository. Wed Nov 25 07:24:47 GMT 2015:ERROR:Failed to publish message. Wed Nov 25 07:24:47 GMT 2015:ERROR:Failed to publish message. java.lang.reflect.InvocationTargetException I will contact the support team with my issues. Thanks.4.8KViews0likes3CommentsUnexpected error when running test case that has groovy test step in 1.5.0
Hi, I get the following error appearing on the logs for a test case with the groovy test step is not completing (steps remain greyed out): Wed Nov 18 08:04:34 GMT 2015:ERROR:Error notifying listener after run java.lang.IllegalStateException: Test history is disabled at com.eviware.soapui.impl.wsdl.history.DefaultLatestRunsProvider.a(DefaultLatestRunsProvider.java:95) at com.eviware.soapui.impl.wsdl.history.DefaultLatestRunsProvider.getLatestRun(DefaultLatestRunsProvider.java:138) at com.eviware.soapui.impl.wsdl.panels.testcase.ProWsdlTestCaseDesktopPanel$InternalTestRunListener.afterRun(ProWsdlTestCaseDesktopPanel.java:921) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.notifyAfterRun(AbstractTestCaseRunner.java:316) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalFinally(AbstractTestCaseRunner.java:188) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalFinally(AbstractTestCaseRunner.java:1) at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:154) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) The test history is disabled due to feedback I got on a previous post reply: Re: Test Case not completing gracefully when Groovy Test Step accessing database.Solved4.8KViews0likes5CommentsRe: JSON Response tab displaying decimal values incorrectly compared to the actual RAW JSON Response
Thanks Samy, It was actually me that made the original post to the forum. Forgot that I had done it. Will try it out in 1.5.0. At the moment I am currently running 1.4.1 as I am having issues in 1.5.0 seperate to this.4.9KViews1like1CommentJSON Response tab displaying decimal values incorrectly compared to the actual RAW JSON Response
I have a REST API that returns JSON. See an example of a response below: "Lines": [{ "Amount": 5.0, "Cashback": 0.0, "Change": 0.0, "Forfeit": 0.0, "InclusiveTax": 0.84, "PaymentMethodId": 44, "ReceiptNumber": "24/0136", "Tip": 0.0, "CLMAccountType": 3, "Id": 10977524091755401, "Seats": [], } As you can see the RAW Response contains a decimal place for Amount, Cashback, Change, Forfeit and Tip. If I view this on the JSON tab in SoapUI NG Pro (Ready API 1.4.1), the decimal place is not getting displayed: "Lines": [ { "Amount": 5, "Cashback": 0, "Change": 0, "Forfeit": 0, "InclusiveTax": 0.84, "PaymentMethodId": 44, "ReceiptNumber": "24/0136", "Tip": 0, "CLMAccountType": 3, "Id": 10977524091755401, "Seats": [], } Is this a known issue(or limitation) in SoapUI? If it is an issue is there a fix planned? Thanks,Solved5KViews0likes4CommentsRe: Test Case not completing gracefully when Groovy Test Step accessing database.
Hi, I have got time to peform the supplied steps and I got the following error now appearing on the logs, my test case with the groovy test step is not completing (steps remain greyed out): Wed Nov 18 08:04:34 GMT 2015:ERROR:Error notifying listener after run java.lang.IllegalStateException: Test history is disabled at com.eviware.soapui.impl.wsdl.history.DefaultLatestRunsProvider.a(DefaultLatestRunsProvider.java:95) at com.eviware.soapui.impl.wsdl.history.DefaultLatestRunsProvider.getLatestRun(DefaultLatestRunsProvider.java:138) at com.eviware.soapui.impl.wsdl.panels.testcase.ProWsdlTestCaseDesktopPanel$InternalTestRunListener.afterRun(ProWsdlTestCaseDesktopPanel.java:921) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.notifyAfterRun(AbstractTestCaseRunner.java:316) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalFinally(AbstractTestCaseRunner.java:188) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalFinally(AbstractTestCaseRunner.java:1) at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:154) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)2.5KViews0likes2Comments