nicoretteOccasional ContributorJoined 14 years ago20 Posts5 LikesLikes received1 SolutionView All Badges
ContributionsMost RecentMost LikesSolutionsRe: Prevent property expansion - escape ${...} This issue is fixed in nightly build Thanks. Re: Prevent property expansion - escape ${...} The issue occurs since ReadyAPI-1.8.0. With previous versions the metioned problem is non-existent. I've reported it to the care team. Thanks. Prevent property expansion - escape ${...} Hello, when using the newest ReadyAPI-version 1.8.0 the escaped '$' does not work anymore. In the following article you recommended using an addionally '$' to escape the '$': https://community.smartbear.com/t5/SoapUI-Open-Source/How-to-escape/td-p/9871 workaround 1: Strangely, if you use three '$' it works. workaround 2: You have implemented a new option to enable or disable property expansion for a specific testStep. BUT: The possible workarounds will cause to change every single testStep and would not be compatible to older ReadyAPI versions. Workaround 2 does also not being the right way to fix the issue globally, e.g. you need to work with mixed states, like at some point you need property expansion but at the other you want to disable it by using the escape option. The mentioned issue can also be reproduced with the latest nightly build. SolvedRe: Build number for Snapshots Additionally the build number should be visible in the software itself and of course being part of the download file name. I would suggest to add the build number in the following cases: download file start logo (currently you can see only Snapshot-m) in the help menu (about-dialog) int the title text of the main readyAPI window So it is not only an improvement to the download site. NullPointerException - getIconPath Hello, Version used: ReadyAPI-1.5.0-m-Snapshot (2016-01-21) (Please add a build number! :mantongue:) Description: If you run a testCase you get the following exception logged to the tab of readyAPI-log (the log repeats for each testStep): Fri Jan 22 09:43:38 GMT 2016:ERROR:Error notifying listener after step java.lang.NullPointerException at com.eviware.soapui.support.UISupport.getIconPath(UISupport.java:1028) at com.eviware.soapui.impl.wsdl.history.LatestTestRunsDataCollector.afterStep(LatestTestRunsDataCollector.java:54) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.notifyListenersAfterStep(AbstractTestCaseRunner.java:273) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:243) at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runCurrentTestStep(WsdlTestCaseRunner.java:47) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:148) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:1) at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:130) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Re: Build number for Snapshots Hello, http://community.smartbear.com/t5/SoapUI-NG/Build-number-for-Snapshots/m-p/112656#M26144 Re: Build number for Snapshots Ok, done. see: http://community.smartbear.com/t5/Ready-API-Feature-Requests/Build-number-for-Snapshots/idi-p/112655 Build number for SnapshotsI would appreciate it if you would add a build number or something like that to your "maintenance build" of ReadyAPI. Currently it is not possible to see whether a new build of a snapshot is available or not.Build number for Snapshots Hello, i would appreciate it if you would add a build number or something like that to your "maintenance build" of ReadyAPI. Currently it is not possible to see whether a new build of a snapshot is available or not. SolvedRe: TestStep "Run TestCase" works different in 1.5.0 (Snapshot) Hello, the software is now working as expected.