DinaE
Occasional Contributor
Joined 4 years ago
User Profile
User Widgets
Contributions
Re: As of v3.60.0 preloading groovy file from script library breaks cross referencing
I have a similar issue in v3.59.0 & 3.60.0. in Jenkins execution, when executing a groovy step that has a reference in the script library, it keeps trying to reload readyapi-settings.xml and the execution finally hangs. 09:57:46,508 INFO [SoapUIProTestCaseRunner] running step [Groovy Script] 09:57:55,426 INFO [DefaultSoapUICore] Reloading updated settings file 09:57:55,428 INFO [DefaultSoapUICore] ReadyAPI settings were initialized from [************\.readyapi\readyapi-settings.xml] 09:57:57,329 INFO [DefaultSoapUICore] Reloading updated settings file 09:57:57,332 INFO [DefaultSoapUICore] ReadyAPI settings were initialized from [************\.readyapi\readyapi-settings.xml]82Views0likes0CommentsjUnit report is showing testcases twice in v3.42.0
This behavior is since v3.41.0 When generating jUnit report in TestRunner. in all-tests.html, some test cases are showing twice. The generated XML documents that contains the details of all testsuite results ( properties & testcase result), are showing the info twice Any idea how to resolve this issue1.5KViews0likes7CommentsManage the projectVersion field in "Setting.xml" , so it doesn't update with every save or reload
Reference Issue - https://community.smartbear.com/t5/ReadyAPI-Questions/Ready-API-3-42-0-automatically-updates-projectVersion-every-time/m-p/240988/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufExBSklETVhHWkdEMTUxfDI0MDk4OHxTVUJTQ1JJUFRJT05TfGhL#M57307 projectVersion value changes everytime a project is saved. When trying to Pull changes from git, setting.xml needs to be committed first, but it re-appears again as a new change, which blocks pulling from git. The "Discard all changes", don't really discard the document.1.4KViews10likes3CommentsRe: Ready API 3.42.0 automatically updates projectVersion every time when loading the project
I'm facing the same issue. It blocks pulling changes from git, because the "setting.xml" needs to be committed everytime. once the changes are pushed, it re-appears again as a new change753Views2likes0Comments