s9goswami
Occasional Contributor
Joined 8 years ago
User Profile
User Widgets
Contributions
Re: Ready Api 2.2.0 - Scipt Library - Update to the Scripts not reflecting
Yes, we are using GIT to checkin and check out the Groovy Code . Are you saying if there are changes done in the same Groovy file , ReadyAPI 1.x will pick up the changes but not Ready API 2.0? I recently posted in Smart Bear and they confirmed its a issue. EXT] Case #00269049: Ready Api 2.2.0 - Scipt Library - Update to the Scripts not reflecting Still I will try in ready API 1.X to try. Thanks for the solution!2.4KViews0likes0CommentsRe: Ready Api 2.2.0 - Scipt Library - Update to the Scripts not reflecting
Yes , but that is very annoying if everytime I have to restart the Tool . As per script library documentation the Tool should recompile / refresh all the classes every 5 seconds which dioesn't seems to be the case? Is Smart Bear putting false documentation or is it a bug? Documentation: Groovy Script Library The Script Library can be used as follows; Specify which directory to use in the SoapUI Preferences tab (default is /scripts). SoapUI will check this directory for files with the "Groovy" extension and compile these upon startup. The directory is then checked periodically (every 5 seconds) for updates and new or existing scripts are compiled and re-compiled if necessary. Scripts should be placed in directories named after their containing package, that is a script in the package soapui.demo should be in a soapui/demo directory under the specified scripts directory. The compiled classes are added to the parent class loader of all Groovy scripts, you can access them as standard java classes. Link : https://www.soapui.org/scripting---properties/scripting-and-the-script-library.html2.4KViews0likes2CommentsReady Api 2.2.0 - Scipt Library - Update to the Scripts not reflecting
Ready Api 2.2.0 - Scipt Library - If i update the scripts meaning change something in the script and then run my tests even after 10 mins , the changes are not getting reflected? Please confirm if this is a bug in Ready API?2.5KViews0likes7CommentsRe: Same Run Time when I trigger test Cases in Sequential and Parallel Run Type
Thanks! Also , I checked with our developer , he confirmed the test steps should not take that long to complete, currently when I execute in parallel test steps are taking 40 secs to complete whereas when the same test step is just trig erred manually it takes around 3.9 secs. Can that be because of the data source test step from where it is reading the data and is it a known issue that if there is a datasource in a test step then when we execute test steps in parallel or sequential it takes the same time. I am asking these because I executed the campaign both in sequential and parallel and the repsonse time is same in both the scenarios1.8KViews0likes0CommentsSame Run Time when I trigger test Cases in Sequential and Parallel Run Type
The Test Cases have 3 TestSsteps. 1. DataSource 2. 1 API Message Call (XML) 3. Data Loop When I am running the teststeps in parallel or in sequence the total time remains same. All TestCases Class Name Status Type Time (s) LSSPermission.SellStrategy Property_SellStrategySearch Success 27.126 LSSPermission.SellStrategy Chain_SellStrategyRateSearch Success 22.993 LSSPermission.SellStrategy Property_SellStrategyFindApplicableSearch Success 26.169 LSSPermission.SellStrategy Property_RPSellStrategyCreate Success 28.489 LSSPermission.SellStrategy Property_RPSellStrategyUpdate Success 27.415 LSSPermission.SellStrategy Property_RPSellStrategyDelete Success 25.876 LSSPermission.SellStrategy Property_RPSellStrategySet Success 20.289 LSSPermission.SellStrategy Property_RPSellStrategyUnset Success 20.111 LSSPermission.SellStrategy Chain_SellStrategyRateCreate Success 20.820 LSSPermission.SellStrategy Chain_SellStrategyRateupdate Success 16.099 LSSPermission.SellStrategy Chain_SellStrategyRateDelete Success 22.336 LSSPermission.SellStrategy Property_RoomSellStrategyCreate Success 19.359 LSSPermission.SellStrategy Property_RoomSellStrategyUpdate, Success 19.154 LSSPermission.SellStrategy Property_RoomSellStrategyDelete Success 20.600 SoapUI Test Results Summary TestCases Failures Errors Success rate Time (s) 14 0 0 100.00% 316.836 Note: failures are anticipated and checked for with assertions while errors are unanticipated. Projects Name TestCases Errors Failures Time (s) Time Stamp Host LSSPermission 14 0 0 316.836 If it really would have been parallel , then the total time would be around 28 ms i.e. the highest time of a testCase1.8KViews1like4Comments